|
Richard Jackson wrote: > > Buck: > > Why is writing a CL program messy? > > Suppose the display had 5 fields called fld1, fld2, fld3, fld4, and fld5. > Suppose that each field was type character and contained a matching field - > the user could supply a blank or an "equal" value. A CL program might be > coded to do the following: This pretty much duplicates what I ended up doing. My biggest concern was NOT "how" to do it, rather, what is a good way that could be followed by either myself or some other poor slob who has to modify it in years to come. I try very hard to keep things simple, both for me and anybody who might follow. There were a number of decent ideas & suggestions and I will end up with a merger of several different ideas.(which is what I wanted) As to Buck's comment about CLP being "messy", I come from the old school on this. Keep it VERY simple and it doesn't look or act "messy". CLP "can" be made to look horrible, but with just a few extra minutes of thought, can be quite elegant. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.