Paul:
The code generator, in my opinion, would have to be architecture
specific. It is possible to generate an object deck/file with COBOL now
(I know, I've done similar work).
I am currently working on a compiler based on COBOL (the source
language). However, I intend to have different code generators
depending on whether I want to generate an object or new source (a
migration tool).
COBOL is an interesting language in that you must do different things
depending on the environment you are in (perhaps I should have said
DIVISION?). The keywords change meanings! (But you must have already
known that).
I wish I could say that I would be interested in what you are doing --
from the viewpoint of being able to test it. However, due to probable
changes taking place in my life, I may not be able to continue the
development I'm currently doing.
The IDE and other things are not really needed in my opinion. Assuming
that one is using the Windoze environment, a DOS window can be used to
run the compiler, and Notepad can be used to view the listing/source
files. I happen to prefer an "SPF" product for source work.
Doing things without a runtime means having to generate a lot of code
from/with the code generator.
File handling will also get to be pretty labor intensive. You will have
to write all the code for handling the file and error processing, etc.
Might I suggest that you first tackle the first level of COBOL sup****t
(Mr. Klein can give you the levels) and then add to that. Be prepared
for the source processor to be rather large and possibly have to be
written in separate subprograms.
Again, the code generator is what concerns me. How and who would write
the generator for each environment?
Lastly, I would love to have an '85 COBOL compiler for Linux. I could
move my whole development environment off to Linux and get rid of
Windoze.
Regards,
Steve.T
|
