Re: [MI400] UPPERCASE vs lowercase variable names

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Hi, Paul:

Well, the QPRCRTPG API only recognizes and accepts
UPPERCASE names, but you can code your source code
so it looks readable and "pretty" with lowercase opcodes,
fieldnames, etc., if you write your own pre-processor.

Since you must use a *PGM to load the source into a
"space" (a big char. array), to pass it to QPRCRTPG anyway,
you just need to translate to uppercase during this process.

The result is a very nice readable MI with "mixed case"...
Of course, you need to be careful NOT to translate "stuff" inside
'quotes' and <brackets>, in case you want to be able to include
any lowercase for literals, etc., so this must use some type of a
state-diagram to keep track of whether inside quotes or not, etc.

I think several people on this list have written just such an MI
"front-end" perhaps one of them will be kind enough to post an
example of this technique here?

And, if you are really "clever" you can add other "features",
such as macro-expansion with substitutions, conditional
assembly, etc. ;-)  This might be a good task for REXX,
since it has excellent string handling and pattern matching
capabilities built-in. ;-)

Regards,

Mark S. Waterbury

----- Original Message -----
> From: "Paul Jackson" <pjackson@xxxxxxxxxx>
> To: <MI400@xxxxxxxxxxxx>
> Sent: Wednesday, March 03, 2004 7:51 PM
> Subject: [MI400] UPPERCASE vs lowercase variable names
>

> Just curious what the general consensus is regarding using mixed/lower
case
> for MI variable names. I have yet to see an example where mixed case has
> been used.
>
> Thanks!
>
> Paul
> _______________________________________________
> This is the MI Programming on the AS400 / iSeries (MI400) mailing list
> To post a message email: MI400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/mi400
> or email: MI400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mi400.
>