Coding can be cumbersome.
The language does not realy matter.
Whether it's good old legacy RPG, ILERPG, SQLRPG or Java.
Handcrafted code is, see Van Dale : "sheer drudgery" or "donkey work" (in Dutch monikkenwerk).
Hard to code, hard to debug and almost never always bugfree.
See this definition of error-prone http://www.wordreference.com/definition/error-prone:
capable of making an error; "all men are error-prone"
As programmer and end-user of this software you are often puzzled by mysteries:
- The mystery of the disappearing database transactions
- The mystery of the disappearing database records.
- The mystery of the disappearing values in a simple list of values.
- The mystery of the NullPointerException.
- and so on ...
In ILEPRG you can declare procedures (having the possibility for local variables),
but you will be bothered by the datastructures to pass arguments.
And beware of the pass by reference of the procedure.
As in Java it always is pass by value.
SQLRPG seems to be a nice option, but do not make coding errors: you will be puzzled by the stuff the (pre-)compiler will spit out.
See http://forums.systeminetwork.com/isnetforums/archive/index.php?t-43004.html:
Too close to Thanksgiving, I think my brain has slowed - possibly someone can point out the obvious that I am overlooking currently.
Last but not least, there is Java, having a number of annoyances and limitations.
In a hybrid environment where Java (web)applications have to communicate with legacy systems, you will definitely end up in an argument: is the bug in the Java code or in the RPG code, or somewehere in between (???).
Then you have to debug, or System.out.println() or DSPLY (RPG opcode) to bring some light in this discussion.
Call al this a challenge!
By the way, that's a nice word, whether, see http://www.wsu.edu/~brians/errors/weather.html:
The climate is made up of “weather”; whether it is nice out depends on whether it is raining or not. A wether is just a castrated sheep.
No comments:
Post a Comment