Re: Does the recommendation against variable names starting with SQL apply to constants?

Rory,

Actually it was a two byte value 'X0' given the constant name cX0...

But don't feel bad, at first glance I thought it was a hex value too. :)

And I will admit that I'm also curious as too what the meaningful name
ended up being.

Charles

On Fri, Sep 3, 2010 at 12:18 PM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:

David,

I'd be interested to know what was eventually chosen as a more meaningful
name than xC0.

Either x'C0' has 'meaning' in the context of the application, so the
constant could be called e.g. HAS_SUB_ACCOUNTS (or whatever), or it's simply
a single byte value. If the latter, is anything gained by giving it a
constant value instead of simply using x'C0'? I *guess* you could call it
HEX_C0, but that  isn't much better than xC0 (IMHO, of course!).

Rory

p.s. I see Scott and Eric have already asked this... I'm always so late to
the game :(
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.