Re: framework question -- JAVA400-L

Hi Joe,

first of all, procedural programming has no means of namespaces, its a nightmare to maintain. Even with ILE and the concept of modules, its far not as readable as OO based code. But i dont want to argue against ILE and its existance, i wrote too many years RPG myself . Also i dont want to argue wether OOP in general is the way to go, because its obvious, i think we discussed if you want to use inheritance over composition. First of all, its not a black or white type of question. It really depends.

If you have an Article which knows how to calculate itself generally, you can create a child of Article, for instance Batharticle, you can easily override the calculation for that, reuse the one the Article has or even mix both caculations. All this in a defined namespace resulting readable code. In procedural languages, you mostly have function-collections with name clashes which call each other quite wildly. To me, working with Inheritance or OO in general makes reading code much easier, its more expressive.

If business programming can be achieved with Java? Look at all those big projects going on, most banking applications are converted to java, ebay is on the way to be converted from procedural stuff to java. IBM is trying to move all its customers to java, so i think, business programming is not so cumbersome at all. If you speak of quick hacking, OO is not the perfect choice, then you are better of with also not using ILE. Then RPG/400 is the way to go ;-) Or use one of these sillly iSeries 4GL RAD Tools like Magic or the other one whose name i forgot.

Marc Logemann

Joe Pluta wrote:

And in any case, the point is not whether inheritance is good or bad,
but whether it is appropriate for business programming.  My position is
that it is not, and that except for the most trivial applications I can
write business logic much more quickly and flexibly in RPG than any
other language.

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.