×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Again, I'm not saying that OO is a bad thing. I'm just saying that it has
its place in the programmer's toolkit like everything else, and I don't find
that place to be writing business rules.
I follow you and I agree. Your response to John makes good sense because
building an OO heirarchy for a few cases will definitely cause maintenance
headaches later on. I think what I am wondering is what if you were to use
Java like you use RPG, where you would essentially have a class with
methods, similar to a *MODULE with sub procs. If we dismiss syntax for a
brief moment, then I think they can offer comparable solutions.
I think John was getting to the point of saying you could use an OO language
to code modular and use the cool language features like overloading and
overriding that are missing from RPG to get to an endpoint quicker.
One of the things I have found with Java vs. RPG is that the Java
development approach likes to have an entire projects worth of classes
checked out so it can compile effectively, where as with RPG, as long as you
have the prototype you can compile. I am guessing this is where Java class
loaders would come into play (have used them very little), but that would be
slightly messy and is an advantage of RPG over Java IMO.
Thoughts?
Aaron Bartell
http://mowyourlawn.com
midrange.com
