Re: SetLL *start

["M. Lazarus" <mlazarus@xxxxxxxx>]

Barbara,

 You're right about the OPEN/CLOSE not making much sense on a 
format.  But the rest of the standard DB I/O should have complete parity, IMHO.

 -mark


At 2/28/2011 06:00 PM, you wrote:
> On 2/27/2011 5:08 PM, M. Lazarus wrote:
> > Is there any good technical (not historical) reason that we still have
> > any opcodes that can't use record formats and file names, for data
> > files, interchangeably? PF's can't contain multiple formats.
> > Multi-format LF's are relatively rare nowadays. The only time it would
> > require differentiation is if a MFLF is used.
> >
> > Is there a consideration to relax that requirement?
> >
>
> Not sure what would qualify as a good technical reason.
>
> I don't think it would be good to simply say that a file name is
> synonymous with its record format name if there is only one format.  At
> least, it doesn't make sense to me to allow say using a format name on
> an OPEN opcode.  But maybe it makes sense to allow a WRITE or SETLL
> *START/*END to a format name if there is only one format.
>
> There hasn't been any real consideration given to relaxing those rules.