Re: [Tiny-cobol-users] Results of COPY work-arounds

[David E. <de...@us...>]

Jim, I can't duplicate any of the problems you have encountered, no
matter what option I try.

What versions of GCC and Bison are you using ?

Jim Morcombe wrote:

 > I tried out your work-arounds to get around the compiler crash.
 >
 > My preferred work-around would have been to play with the path
 > by adding an extra delimited or a dummy path as then I could
 > leave the Cobol source untouched.
 > However, it didn't help.
 >
 > Moving the Copybook into my working directory didn't help either.

Walter suggested not using either '-I' or environment variables on the
command line.
Did you try this option ?


 > Placing the name of the Copybook in Quotes ( COPY "GLBAL-IO-WS")
 > resolved two of my examples.  These were the cases where I'd also
 > managed to get the compiler to work by renaming the Copybook.

By placing the copybook name on quotes, the resource file defined
suffixes are not added to the name.


 > My third example wasn't resolved.  This was the example where renaming
 > the Copybook also didn't allow the program to compile - but when
 > editted the Copybook and commented out a random line, the program did
 > compile.

If you add an extra comment line some where, does the program compile ?


 > All three of these Copybooks were automatically generated by a program
 > that reads through the "FD" for a file.  Hence I am reasonably
 > confident that the examples are  similar and that there are no
 > unique programming error of typing mistakes that exist in just one
 > or two of these Copybooks..
 >
 > It also means that if I have to, I can modify my conversion programs
 > to automatically place Quotes in these COPY statements - but that
 > still doesn't solve the third example.

All these work-arounds are not really a solution, as there is no point
on having compiler features if you can't use them.