Re: [Fwd: gnubol: Record delimiter clause and parse order]

[Tim Josling <tej@melbpc.org.au>]

I think it did get resolved, until this email ;-)

We were going to use the extra syntax of line sequential to
specify this (option (1)).

However I think it would be good to have a way to specify outside
the source code that sequential means line sequential. I am not
fond of inline directives which to me combine the worst of both
worlds of command options and inline syntax. Although it does
allow the program to specify what options it needs to compile, I
guess (most C programmers just put comments at the top if certain
options are needed).

Tim Josling

"William M. Klein" wrote:
> 
> Did this "discussion" get resolved while I was off email (at the J4 and WG4
> meeting)?
> 
> "RECORD SEQUENTIAL" (*not* delimited) is ANSI/ISO conforming (and required)
> 
> "LINE SEQUENTIAL" ("delimited) is a "common" extension on many (most?) UNIX
> (and PC) type environments.  This need NOT be included in an ANSI/ISO
> compiler
> 
> There are two ways of "distinguishing" these two types of files that are in
> common usage. (some compilers support BOTH - with rules as to which overrides
> the others)
> 
> 1) In the Select/Assign clause allow LINE/RECORD SEQUENTIAL in the
> organization phrase.  RECORD *must* be optional - and if nothing is specified
> (at all) for organization, then you should ge RECORD SEQUENTIAL files.
> (Medium "useless" on PCs and UNIX - but "useful" for other COBOL
> applications - and ANSI/ISO conforming).
> 
> 2) A compiler directive to "change" how the ORGANIZATION IS SEQUENTIAL phrase
> is "interpreted".  In ANSI/ISO mode, it is taken as "RECORD SEQUENTIAL" -
> when "overridden" it means LINE SEQUENTIAL.
>

--
This message was sent through the gnu-cobol mailing list.  To remove yourself
from this mailing list, send a message to majordomo@lusars.net with the
words "unsubscribe gnu-cobol" in the message body.  For more information on
the GNU COBOL project, send mail to gnu-cobol-owner@lusars.net.