Re: Same prefixes (was Re: It's That Time Again! etc.)

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Peter,

Yes it might be a challenge to remember where a field value changed if the
field was named the same on the screen as in the file.  However, anyone
experienced in screen programming should be able to handle that.  Are you
saying that would be trickier than, oh let's say, a field whose value
changed because the pointer that it's data structure is based on was
changed?    :-)

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Peter Dow" <maillist@dowsoftware.com>
Sent by: rpg400-l-admin@midrange.com
08/22/2002 12:05 PM
Please respond to rpg400-l


        To:     <rpg400-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: Same prefixes (was Re: It's That Time Again! etc.)


Hi Doug,

You are correct that until qualified data structures, an opcode like EVALC
wouldn't make sense.  But until externally-described files and the PREFIX
keyword on F-specs or Data Structures, hardcoded field name prefixes were
(IMO) a necessity. Now we have some flexibility, which is not to say that
it's not still a good idea, especially since we have slightly longer field
names, just that it's not so much of a necessity.

I have run across programs that used the same field names for the disk and
display files, so I do recognize that it's not a "necessity", but with
that
style program it's a bit harder to keep track of where a field's value
came
from, especially when you didn't write it.

Regards,
Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 522-3214 cellular
909 793-4480 fax


----- Original Message -----
From: "Douglas Handy" <dhandy1@bellsouth.net>
Sent: Wednesday, August 21, 2002 6:13 PM
Subject: Re: Same prefixes (was Re: It's That Time Again! etc.)


> >This was generally considered a good idea way back in the days of yore
(i.e.
> >before externally-defined files),
>
> Although I did in fact start this practice before the S/38 existed, why
do
> externally described files change whether it is a good idea?  The
problem
is
> name collissions in RPG, and until qualified DS names that was true in
all
> flavors of RPG.
>
> Qualified DS names makes for a more elegant solution, but how do
external
> definitions vs program described files weaken the argument for field
name
> prefixes?
>
> Am I not seeing the forest for the trees?
>
> Doug



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.