|
On 18/11/2006, at 12:46 AM, AGlauser@xxxxxxxxxxxx wrote:
Single quotes are only required when: a) The value contains special characters like spacesb) The value must contain lower-case characters (and CASE(*MIXED) isnot specified)I think point b) contradicts that first bit. It seems to me that, if Iunderstand correctly, the solution to the problem that the developer had (which is a variable being interpreted as a literal if the & is forgotten)is to use mixed case for variables.
No contradiction. If the command parameter has the default of CASE(*MONO) specified then lower-case characters are folded to upper case unless enclosed in single quotes. If CASE(*MIXED) is specified then the characters are not folded and passed as typed.
You're suggested solution will not work. If a coder forgets the single quotes the command analyzer will simply pass the mixed-case value (if CASE(*MIXED) is specified) or fold into upper-case (when CASE(*MONO) is specified). Either form will be accepted by the CL compiler.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.