RE: SQL pre-processor (was RPG IV release levels and complexity)

 >> Basically, just as it's unacceptable for SQL in Rochester to depend on
the compiler for SQL processing, we in compiler development simply don't
want that responsibility either!

I know that Hans - and I didn't suggest anything of the sort.  The only
dependency placed upon the compiler should be for it to recognize the SQL
block.  The syntax checkers do that today so it is hardly arduous.

It would take changes in the compiler and changes in methodology by the
pre-compiler, but there is no need for either party to know the others job.

 >> Jon: I thought we were through with rehashing this old debate.

Heck we haven't finished with Move in /free so why this one <grin>  I think
the debate needs to continue if for no other reason than to convince
Rochester that they have done a lousy job of keeping the pre-compiler
up-to-date so far and that this is not acceptable.  They are either serious
about getting people to use embedded SQL or they are not.  Despite the
current efforts, the evidence to date is that they are not.  I think it
important that we keep the pressure on to ensure that the changes don't stop
here.

Hans:  As you know very well my comments are not directed at Gina, but at
the decision makers behind her who caused this whole mess.

Jon Paris
Partner400
www.Partner400.com