Louis Krupp

Another attempt at the StackExchange link: https://unix.stackexchange.com/questions/609693/feeding-a-command-using-file-redirection-or-pipe-doesnt-always-work/610101#610101

Failure when compiled with optimization

Rev. 2340: Syntax error on screen items consisting of LINE or COL

A bit of background: About three years ago, I proposed a patch to screenio.c that would have fixed at least part of the problem with the Screen Section OCCURS clause. Two years later, after other intervening (and incompatible) changes had been made to the file, there was an attempt to integrate my patch. The result was that my patch no longer fixed the problem at all. Speculating that if there were an automated way to test GnuCOBOL screen output and compare it to a reference implementation, there...

Once more unto the breech... Using OpenVMS COBOL as a reference implementation along with a Python program that reads ANSI terminal commands, builds a virtual VT100 screen and produces a text file representation, I've collected a few Screen Section test programs along with what I'm fairly confident are correct output files. (DEC was pretty good at this sort of thing.) "make screentest" runs the programs, runs the output of each one through the same Python program, and does a diff with the reference...

I looked at this a couple of years ago. I had a patch (see attached) that fixed at least part of the problem at the time, but intervening changes to screenio.c have made it pretty useless now. When Edward got back to me last October, I said I'd look at it, but I got distracted by other things. The problem seems to be that cob_screen_puts() calls get_screen_item_line_and_col() to return the static line and column associated with an item, and those are assigned to cob_current_y and cob_current_x. This...

I forgot to mention: % svn info Path: . Working Copy Root Path: /home/louis/gnu-cobol-2.0...

Build error