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

[Jim M. <ro...@vi...>]

Dave,
I am using gcc version 3.2 and bison version 1.35

here is the result of a "gcc -v"

[jim@byrlin3 jim]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --enable-shared --enable-threads=posix 
--disable-checking --host=i386-redhat-linux --with-system-zlib 
--enable-__cxa_atexit
Thread model: posix
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)


Here is the result of a "bison -V"

[jim@byrlin3 jim]$ bison -V
bison (GNU Bison) 1.35

Copyright 1984, 1986, 1989, 1992, 2000, 2001, 2002
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[jim@byrlin3 jim]$




David Essex wrote:

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