[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU-COBOL] Let's go!



Laura,
I certainly endorse the idea of getting started. I think it is a
good idea to just check if everyone is comfortable with these
directions as well.

Not using Flex. I hand wrote a scanner twice and I strongly
suggest that Flex is a better idea (OK you have to handle the
reference format, continuations etc manually - but it saved me a
ton of work in the 'preprocessor' - all coded and 70% tested). I
guess as long as you make it strictly Flex compatible we can use
Flex later if/when we tire of writing a scanner by hand.

Using Bison - I agree I think but there was a lot of discussion
about Bison can't hack it. In the preprocessor, I had troubles
with reference modifications and I had to do some hacks (couple
of hundred lines extra). Chad had some significant issues with
this and I would like to hear from him what the problem areas
will be and then we can discuss how we would address them if they
can reasonably be addressed.

C-library interfaces - absolutely agree - we need to define
interfaces and get people working on libraries. To maximize
parallel work, we should put as much as possible into the
oibraries initially and then move function into generated code in
the optimisation phase as needed - even 'move' can be a libraru
when you think about all the permutations and combinations of PIC
clauses etc.

Perhaps also we should set some short term objectives eg COBOL 85
nucleus level 1 with no extensions and performance be damned ie
focus on functionality.

Attachments

Grammar pieces: I think for getting something done we need to
limit to say nucleus level 1 at first. Who is writing the
scanner? Need to define the token IDs and what info 'flex' will
provide from the optional things (line number for example).

Skill set:
Flex - yes, reasonable comfortable
Bison - yes, quite comfortable
C - yes, fully conversant, 100,00s of lines since 1987.
COBOL - yes, fuly conversant with most aspects, 100,000s of lines
since 1978)
Copy of standard - yes, also copy of the clarifications issued by
the committee
Development environment - Linux 2.0 (this is something we should
find out from everyone - if we are using different tools we will
have troubles)

Tim Josling

Laura Tweedy wrote:
> 
> First, a train of thought and some resolutions.
> Then, please read and respond to the attachments.
>...


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