Good, now I can try it. How do you deal with copy books? I really like that you remembered that Cobol should be compilable in less than 16K of ram. Multiple stages really help understandability here.
Stephan
Hi. Copy books - I basically ignore them. Usually I tried to get the listing after the compiler had handled the copybooks (and any macro expansions) - made my life easier. My take is that this is a parser - not a compiler. After parsing, then other interesting things can happen - but for my work, I didn't really need to figure out how to handle copy books.
You might be interested in another little package: PunchedCards. On SqueakMap http://map.squeak.org/package/2ee288c8-7041-4801-ab4a-90e9b9d93469/autoversi... Should be able to show any oft the CobolCard's in from the initial parsing stage as a punched card, ready to be read. Useful? Probably not, but fun.
May or may not run in Moose - haven't tried it yet (don't know if a required piece has shifted in Pharo yet or not, mainly).
On Tue, Jul 22, 2014 at 2:31 AM, Stephan Eggermont stephan@stack.nl wrote:
Good, now I can try it. How do you deal with copy books? I really like that you remembered that Cobol should be compilable in less than 16K of ram. Multiple stages really help understandability here.
Stephan
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Chris Cunningham -
Stephan Eggermont