|
Hi Dave, On Tue, 26 May 1998, David Gibbs wrote: > > At 01:42 AM 5/24/98 , jovic@calcna.ab.ca wrote: > > Passing command name as a parameter is not an option. > > Just out of curiosity... why is passing a command name not an option? You > can code the command name as CONST data in the command. > Well ... if you must know, there are two reasons: 1. That's a kind of solution which most of first year college students could come up with. I'm looking for something nicer and more AS/400 specific; I still believe, there have to be some beauty in anything one does. 2. That will force me to change all main programs also (to adjust number and types of parameters, if I put it in the first position), or it would force me to receive all parameters in validation programs (if I place it in the last position), which would further lead to more than one validation program (not all comands have same number of parameters, and I validate only first two) ........ I don't wont to confuse other developers; they already have enough troubles with me because of 1. :))))) huh...? Take care, Vanya +--- | 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.