Re: gnubol: Cobol internals consideration

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

I agree. We can plug into the GCC back end and they will generate
the code for us. Saves writing half the compiler. It also gives
you a debugger with a little work for the new data types.

Tim Josling

Glen Colbert wrote:
> 
> Writing an assembler in 'C' is a different thing than writing a Cobol to 'C'
> translator.  The compiler should not require a separate 'C' compilation to
> create an executable (although most generate assembler output).  If GNUcobol
> is going to interface into the standard debugging tools as Cobol (and not as
> 'C'), I believe that this approach will be required.


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