Re: Is the 4gl 4.12/13/whatever compiler a bit smarter

> This program will *NOT* stop with an error message in function b. > It also really annoys me that I have to remember to put > WHENEVER ANY ERROR CALL serious_error in the front of every program > module if I want to use my own error handling routine. WHENEVER ERROR is a *compiler directive*, NOT an executable statement. So the relevant error handling applies between the physical lines of code in your modules, *not* between the points in time at which you execute them. > or: > DISPLAY l_variable + 1 TO screen_field `------v-------' > 4GL seems incapable of coping with this sort of expression evaluation > anywhere. You have to assign the expression to a variable first, then display that variable. > or: > Why the hell can't I use the PRINT command in a function? It sure > would > save some code duplication at times! Because PRINT is a special statement that only works in report formatting functions. Think yourself lucky, in all the versions of Oracle I've used the report writers are completely separate software products, rather than Informix's approach of sending data to a special kind of function. > THE QUESTIONS: > Are any of these things considered bugs? No. > Are any of these things likely to change in future versions? > What is the ETA of 4GL++? > Is 4GL++ going to be backwards compatable with 4GL? Can't answer those except that I understand the answer to the last one is intended to be "yes", but don't take that as definitive. akent@cix.compulink.co.uk (Andy Kent) ------------------------------------- 44 272 742815