Re: Free format vs SQL

Any chance of them allowing
/exec-sql
...
/endsql

within the free format?  Or do away with the silly /endsql because the
semicolon will suffice.  A CASE tool that we use (AS/SET, primitive at
best) does the following in their action diagramming.
execsql     your sql statement here
and converts it into a really badly spaced / sequence that RPG400 requires.
(RPG400 doesn't require the bad spacing, that is a 'feature' of the case
tool.  I especially loathe the continuation of verbs, midword, from one
sentence to the next.)
Writing our own subprocedures
execsql(your sql statement here)
sounds a bit hairy
But I am sure that those fine precomiler folks should be able to handle
execsql( your
         sql
         statement
         here);
Ya think?

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    boldt@ca.ibm.com
                    Sent by:                To:     rpg400-l@midrange.com
                    rpg400-l-admin@mi       cc:
                    drange.com              Fax to:
                                            Subject:     Re: Free format vs SQL

                    09/07/2001 06:54
                    AM
                    Please respond to
                    rpg400-l






rob wrote:
>I think we had errors when we did
>C/END-FREE
>But
> /END-FREE
>was okay.

Why is that?  Well, /END-FREE obviously is valid only within
a free-form block.  And within a free-form block, column 6
must be blank.

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com

_______________________________________________
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.