RE: gnubol: Re: Cobol Compiler Suggested Tasks

["William M. Klein" <wmklein@ix.netcom.com>]

Matthew Vanecek (et al),
 The major area of "change" between the '85 Standard and the draft Standard
(for sequential files) is in the area of "new" file-sharing/record-locking.

As many (most?) of the UNIX/WinTel COBOLs already provide something similar,
you may want to look at how easy/hard it will be to include that.

Another area where the draft is SIGNIFICANTLY different from '85 relates to
enhancements to the CODE-SET clause and how this works with the new FORMAT
clause.  This is for "auto-magic" conversion of files from one character set
to another.  This would probably be a "nice" to have for Unicode/ISO-10646
uses "today" - but is certainly something that you NEED NOT worry about in
creating an '85 compatible compiler.

P.S. there is also a reasonable amount in the '85 (and draft) Standard
sections on Sequential I/O that relates to "tape" files.  Personally, I would
suggest that you SKIP this (at least in the first implementation).  This is
(mostly) in the hardware dependent ('85 Standard) or Processor Dependent
(draft) lists, so it should be pretty easy to spot.

Finally, there were a couple of items related to sequential I/O that were
obsolete in '85 (so they won't even appear in the draft).  I can look those
up - if you want to know about them, but again, I wouldn't call them a "high
priority".

> -----Original Message-----
> From: owner-gnu-cobol@wallace.lusars.net
> [mailto:owner-gnu-cobol@wallace.lusars.net]On Behalf Of Matthew Vanecek
> Sent: Tuesday, May 09, 2000 6:51 AM
> To: gnu-cobol@lusars.net
> Subject: gnubol: Re: Cobol Compiler Suggested Tasks
>
>
> Tim Josling wrote:
> [SNIP]
> >
> > Matthew Vanecek: Runtime routine for FILE IO for sequential file.
> > Note that most of the compilers support 'line sequential' which
> > is not in the standard
> >
> [SNIP]
>
> This sounds good. I'll look over what you've done already, and see what
> kind of ideas I can come up with.  Also, the latest draft standard is
> available (for free!) for download.  I don't think it's changed much in
> this area, but I'm going to read the I/O section for files and see
> what's up.
>
> Hmm, I wonder if we could wrangle some type of VSAM fs out of all
> this....that would really rock. :)
>
> --
> Matthew Vanecek
> Visit my Website at http://mysite.directlink.net/linuxguy
> For answers type: perl -e 'print
> $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> *****************************************************************
> For 93 million miles, there is nothing between the sun and my shadow
> except me. I'm always getting in the way of something...
>
> --
> 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.


--
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.