|
I agree that to be able to "tweak", in this context, has not much use (e.g.-snip really long source code example- :)
you want day 1 to be sunday).
But if you want to use SQL for everything if there is some function
provided, then why not throw RPG out altogether and program everthing in
SQL/PL?
It's not the "preprocessor" machinery, it's having all kinds of
dependencies etc. For example you need to change the member type from RPGLE
to SQLRPGLE, because you need to do some date math. When the program runs,
the SQL runtime machinery is also initialized, just for some date maths,
which in every other language you don't need to resort to embedded SQL
Maybe it's optimzed that if you only call some functions it has no
overhead, but i don't know, etc..
Use SQL for DB tasks, use RPG for the rest.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.