Re: RPG - Software Architecture / Best practices

Dieter,

OO, as you probably know, has nothing to do with service programs.

It's plain old modulare programming we had for ages already with C, Pascal
etc.
Nothing wrong with that by the way, glad we have it now on i.

But i think it works confusing for somebody who doesn't have experience
with modular programming (and OO), if you try to compare the two. OO is a
"next level" way of modular programming. Talking about inheritance (which
is not a canonical part of OO.

Information hiding, separation of concerns, etc, are important concepts to
actually make good use of service programs. These concepts are not tied to
OO. It's better to focus on these concepts, and if these concepts are clear
and a programming has expererience with it you can introduce OO related
concepts.

But saying that service programs are like OO but without inheritence etc is
confusing. And maybe scary...



On Sat, Jan 26, 2013 at 10:57 AM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

Charles,

@RDP: it looks like Eclipse, but the most important features are missing.
Especeally the complete Refactoring capabilities.

@layered Architecture: you would end up with SRVPGMs, to get some taste of
OO, but RPG doesn't have Interfaces, Inheritance, Overloading and you can't
controll instantiation of a SRVPGM, you will get only one, or it's short
living.

@test driven development: RPG doesn't have tools supporting this, you
would have to start with writing your own development tools.

Dieter
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.