Re: array ?

Dennis Pimple (dennisp@informix.com) wrote: > spitz@GANS2X.ana.med.uni-muenchen.de (Richard Spitz) writes: <lines deleted> > >I have always been angry that this doesn't work with DISPLAY ARRAY. I am > >sure that it would be easy to implement BEFORE ROW/AFTER ROW etc. in > >DISPLAY ARRAY just as in INPUT ARRAY, and this has been near the top of > >the wish list for 4GL for a long time. Why has it not been implemented? > My 2 deutchmarks worth: DISPLAY ARRAY is a "quick and dirty" way to > displaying an array's worth of data. All functionality you want for > DISPLAY ARRAY are available by coding it as INPUT ARRAY and disallowing > input via NOENTRY fields and the like. My point is: where do you stop > when adding features to DISPLAY ARRAY that makes it look more and more > like INPUT ARRAY? If you need more control over the display/actions of > an array than DISPLAY ARRAY offers, code it as INPUT ARRAY. Added > functionality for DISPLAY ARRAY has never be high on *my* 4GL feature > request list; I'd rather R&D spend time on adding features we can't do > in any way; like get_fldbuf() did for us. Well, since it seems to me that the functionality of DISPLAY ARRAY is merely a sub-set of the functionality of INPUT ARRAY, it should have been trivial to fix DISPLAY ARRAY -- just don't take so much *out*. -- Jim Holbach | The more I know, jholbach@crl.com | the less I understand. San Antonio, TX |