Re: More SQL precompiler

[rob@xxxxxxxxx]

Many of the limitations of the precompiler in ILE RPG are also found in
those other languages:  local variables, arrays in a PREPARE statement,
etc.  Thus it is not a limitation of just the ILE RPG precompiler.

John, I am not arguing with you.  How do we go about getting that change
made?  In theory you could submit a DCR that is summarized by your
statement
"If the precompiler is choking on syntax, data types, subprocedures, or
other elements within the source member that are valid host language
statements, then the product simply isn't functional."  Pretty it up a
little and there you go.  Do you have any other suggestions on how to
express this to IBM?


Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "John Taylor"
                    <jtaylor@rpg2java       To:     <rpg400-l@midrange.com>
                    .com>                   cc:
                    Sent by:                Fax to:
                    rpg400-l-admin@mi       Subject:     Re: More SQL 
precompiler
                    drange.com


                    03/21/2002 04:39
                    PM
                    Please respond to
                    rpg400-l







Rob wrote:

> Frankly I agree.  And that was my original thought when I entered my
> concerns into the IBM arena.  Perhaps I was seduced once I went into
there.
> I think I couldn't see the forest because the trees were in the way.
>
> How do you suggest you get them to actually accept that the dang
> precompiler should just accept everything that the language supports?

FWIW, my view of the forest looks like this:

The purpose of the SQL Precompiler is to read a source member written in a
host language, find all the SQL statements within that source member, and
convert those statements to run-time API calls in a syntax valid for that
host language. If the precompiler is choking on syntax, data types,
subprocedures, or other elements within the source member that are valid
host language statements, then the product simply isn't functional.

At the present time, there are SQL Precompilers available for the following
languages:

- C/C++
- Cobol
- PL/1
- Rexx
- RPG
- ILE RPG

Particularily noteworthy, is the fact that IBM distinguishes between RPG &
ILE RPG in all of the documentation related to embedded SQL programming.
This is evidence of the fact that they recognize those host languages as
having distinctly different capabilities and, therefore, requirements.

Presently, the precompiler does not allow us to utilize the full
capabilities of the ILE RPG compiler. Indeed, the functional disparity
grows
with each new release! Therefore, I suggest that there is no need to talk
about DCE's or customer enhancement surveys until the product has reached
the point where it fulfills the fundamental requirements of a precompiler.
Fortunately, they don't need a DCE to determine what those requirements
are.
All they have to do is consult the ILE RPG Reference Manual.


John Taylor



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.