RE: Externalizing I/O was RPG read loops

>> BTW, when is RPG going to allow us to use the longer ALIAS field names in
>> our programs?

I agree with you there! Wanted that for years. How tough can it be?

-----Original Message-----
From: Paul Morgan [mailto:pmorgan@xxxxxxxxxxxxxx]
Sent: Wednesday, February 02, 2005 2:20 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Externalizing I/O was RPG read loops


Rob,

It doesn't.  Congrats on having long field names.  Many applications still
use six character field names.  Procedure names aren't limited to six or ten
characters.  Spelling out a procedure name is a lot better than a ten
character field name.  Can't do a one character typo unless the procedure
names are very abbreviated.  I could have a typo in

EMFNAM = WorkLastName;

when I wanted to use EMLNAM.  With a setter I'd have to write

SetFirstName( WorkLastName );

instead of

SetLastName( WorkLastName );

It can still be a problem but it's more noticeable and won't happen as
often.

Paul

BTW, when is RPG going to allow us to use the longer ALIAS field names in
our programs?

--
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

> How will this not stop a typo
> MyDbField=MyWorkField;
>
> But this will?
> setMyDbField(MyWorkField);
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com