RE: IFS in RPG

Seems to me that bifs to wrap the Unix Type file APIs wouldn't be a bad
thing.  It would standardize things nicely.  OTOH, the prototypes aren't
arcane.  I don't think being able to put the file name on an F spec would be
as helpful as it may sound.  One thing you lose immediately is the ability
to use string variables for file names.  I've always found that to be the
only annoying tradeoff in RPG file I/O.

Stream files are harder to deal with than database files.  There's no way
around it.  Opening, closing, reading, and writing are the easier parts.
The harder part is parsing and manipulating the data once you get your hands
on it.



> -----Original Message-----
> From: Peter Dow [mailto:maillist@dowsoftware.com]
> Sent: Thursday, July 11, 2002 1:38 PM
> To: rpg400-l@midrange.com
> Subject: Re: IFS in RPG
>
>
>
> ----- Original Message -----
> From: "Alan Cassidy" <acassidy@pioneermetals.com>
> Sent: Thursday, July 11, 2002 1:30 PM
> Subject: Re: IFS in RPG
>
>
> > Plus, we maybe could assume that the implementation could
> cause implicit
> or
> > appropriate locks on the files...
>
> Or you could have a Filespec keyword LOCK(*EXCL) or LOCK(*SHRRD).
>
>
> > Besides using a things like read-delimited into an
> externally described
> DS...
> >
> > Hey, you could even do a primary-file read-delimited into
> ext-described-DS!
> > <big grin>
>
> Exactly!
>
> Peter Dow
> Dow Software Services, Inc.
> 909 793-9050 voice
> 909 522-3214 cellular
> 909 793-4480 fax
>
>
>
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise
recorded by The Sharper Image corporate e-mail system and is subject to
archival, monitoring, review by and/or disclosure to Sharper Image security
and other management. This message is intended only for the use of the
addressee and may contain information that is privileged and confidential.
If you are not the intended recipient, dissemination of this communication
is prohibited.