Vincent (Bryan) Coen

journ and others

cntlines readne

change the pic 9 to pic z. On 29/05/2026 17:55, Guido Rebry wrote: I copied the program screen01.COB (sent here on Sat Apr 25, 2026 02:50 PM, topic 'Compiler warning', 'thread 941d670883' to screen02.COB and changed a few lines. (fi, I added 2 'blank when zero' clauses) When compiling screen02.cob using GnuCobol 3.2 (64 bit, Arnold Trembley package) I now get 2 different "false?" warnings : Q:\COBOL\SOURCE\SCREEN02.COB:24: warning: 'nmbr1' does nothing [-Wothers] 22 | 02 pic x(01) value space 23...

My programming history goes back to 1963. So compilers : EE - Leo 3 1959-1964+ IBM from 1963 ANSI Cobol - 360-> OS/VS - 360/70. OS/VS2 and later ditto ICL 1900, 2900, 3900 compilers.from 1968/9. from 1970 Burroughs - what was used ? Honeywell ditto Cray ditto CDC ditto and others I have forgotten Some of the above was worked on at a similar time as I also worked as freelance Almost all them could cause the same issues with things like missing periods of other typos. As fo producing a lot of error...

Sorry to dissolution you but many compilers can get lost in a similar way - a compiler is not a mind reader. On 25/05/2026 15:02, Ralph Linkletter wrote: I was looking for relief for a user base transitioning from IBM or Micro Focus COBOL to using GnuCOBOL. A simple syntax error can result in 1000''s of meaningless diagnostics. Apparently the parser, or scanner, or Bison, or YACC gets "lost". Meaning the parser scanner cannot advance to a valid COBOL token after encountering some set of syntax or...

1232

New corrections on some points of the manual

Failed build - missing "end smallexample" had "end small example" Took me 30 minutes to find the issue. Please be more carefull.