Re: [open-cobol-list] Output listing.

[John Culleton]

On Friday 12 November 2010 14:31:38 Vince Coen wrote:
> On Friday 12 Nov 2010, John Culleton wrote:
> > On Thursday 11 November 2010 17:36:09 Sergey Kashyrin wrote:
> > > And actually that brings another good topic - I actually want
> > > to see the comments lines in the COBOL listing, as well as in C
> > > code ! I think that would be nice to achieve
> > >
> > > Regards,
> > > SK
> >
> > Deleting comment lines seems to serve no purpose, I agree.
>
> I also agree with including the comment lines for a listing.
> I did have all source code listed in cobxref but the code to
> process the copy statements was removed when I switched to using
> the input produced by cobc.
>
> A simple solution would be for cobc to have a switch to output the
> full source to a file that can be printed. If Roger does not do
> that for v2 I will reinstall the code that processed the original
> source but I will have to add some stuff to deal with copy
> replacing which I did not bother with on that specific version.
>
> I will look at it in the next month or so to pass to the print file
> all source prior to compressing (removing all instances of more
> than one space) the code before the xref process starts, so
> hopefully that will resolve your issues with cobc. However I do
> need to look again at the code base to try and clear out some of
> the bugs in cobxref.
>
> Vince

How are you coming with this project? I recommend the Tiny COBOL 
listing as a good model to follow. It handles comments, copy files, the 
whole bit. 
-- 
John Culleton
Create Book Covers with Scribus:
http://www.booklocker.com/p/books/4055.html
Typesetting and indexing http://wexfordpress.com
book sales http://wexfordpress.net
Free  barcode: http://www.tux.org/~milgram/bookland/