Re: Need work-around for bug 26390

In article <5m47q4$bgq@cssun.mathcs.emory.edu>, Joseph Cullipher <joseph@cannonexpress.com> wrote: >Hi all, >I am looking for sometype of work-around for this bug. This bug clears the >screen everytime the run command is executed. I found out that it was fixed >in 4GL 6.02 but I'm using 6.00. Reading about the bug it said it was caused >by the reset string in the termcap entry. I removed that and I still get >the same results. This bug was fixed in 4.14/6.02. New syntax was added to allow the programmer to control whether or not the screen clears. Stealing from Jonathan's assertion: 1. Extend the RUN statement: <run-statement> ::= RUN <command-specifier> [ <run-screen-mode> ] [ <run-control-mode> ] <command-specifier> ::= <literal-string> | <string-variable> <run-screen-mode> ::= <line-form-mode> <run-control-mode> ::= WITHOUT WAITING | RETURNING <integer-variable> 2. Extend the OPTIONS statement, adding to more clauses: <option-specifier> ::= [ ... ] | RUN <line-form-mode> | PIPE <line-form-mode> > This clearing of the screen is extermely annoying in >one program in which file locations and permissions need to be checked. Offhand, I'd say your workaround is to not use the RUN statement and instead do these tasks via system calls (e.g. stat()) in a C module. -- Alan Denney aland@informix.com yosemite@netcom.com Informix Platform Engineering "I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachment of those in power than by violent and sudden usurpations." -- James Madison