Re: Java and OO Concepts

john e wrote:

Joe wrote:

In fact, I prefer RPG procedures because I can pass multiple
input/output parameters; it's a very nice technique.

You can have multiple I/O parameters in Java easily by using a
"value holder" object, e.g. ValueHolder which has simply one public property, "value". Simply pass a valueholder for each I/O parameter and replace "value" with the object to be returned.

But not primitives. In order to pass an updatable integer, I have to create an Integer, set the value, pass the object to the routine, then unwrap it in the called routine and use it, set it back into the object, and then unwrap it in the caller. With autoboxing and inlining you might argue that it's pretty transparent to the programmer, but it's something I don't even have to worry about in RPG.

It's just one more way Java (and OO in general) gets in my way as a programmer. That's why I really like EGL; it supports bidirectional parameters as well, even at the primitive level.

Joe