[open-cobol-list] Re: several problem issues with 0.32

[Roger While]

1)  Actually this is a "severe" warning. It is actually saying that
NO code will be generated. Upcoming CVS will have FUNCTION's.
I am of the opinion that, if something is not implemented, this should
be an error. This will be so in a forthcoming CVS update for
non-implemented code.
2) Known problem. Has been fixed in CVS.
3) There is a "Bugs" section.
Firstly, check if the problem is reproducible using CVS version.
Depends. I would do the following -
Can I reproduce this with a small test program ?
If so, put the program inline in the mail.
If not, and the program (plus copy procs) is more than ca. 150-200 lines
create an attachment; otherwise inline in the mail.
Depending on where it blew up, you may have :
a cobxxxxxx.cob (xxxxxx is random) in the /tmp or $TMP/$TMPDIR
(if set) directory. Send/attach this.
a prog.c and prog.c.h (prog = basename of cobol source)
Send/attach these.

P.S. Applies to everyone -
Please refrain from sending signatures.
I have no objection on private mails, but not on lists.

Roger


> I have several questions that may result in reporting bugs.
> 1. warning issue- running:
>         cobc --std=mvs -Icopy -c file.cob -o file.o
> produces the following WARNING:
> file.cob: In paragraph '5050-CREATE-CBLOG':
> file.cob:299: warning: 'FUNCTION' not implemented
> if this is a warning AND i have not specified any warnings to be emitted 
> then
> why is this happening?
> 2. c output issues- running:
>         cobc --std=mvs -Icopy -c file2.cob -o file2.o
> produces this:
> /tmp/cobNVeQ2m.c: In function `ML001_':
> /tmp/cobNVeQ2m.c:31: error: `f' undeclared (first use in this function)
> /tmp/cobNVeQ2m.c:31: error: (Each undeclared identifier is reported only 
> once
> /tmp/cobNVeQ2m.c:31: error: for each function it appears in.)
> /tmp/cobNVeQ2m.c:31: error: initializer element is not constant
> /tmp/cobNVeQ2m.c:31: error: (near initialization for 
> `h_TSQ_FILE.record_size')
> 3. cobc segmentation fault- i get a cobc segmentation fault compiling a
> different file.  is there cobc make or configure options i can set to make 
>
> certain that the most debugging info is available in the core dump?  how 
> do i
> report this kind of error?