Re: Why use PHP? What are the disadvantages?

I don't understand what you mean by scope executes asyncrone?

Scope isn't that hard to understand, and already exists in RPG sub
procedures anyway?

May be RPG doesn't need full OO abilities, but all I can say is my bext most
flexible RPGIV code has been written in a pseudo oo fashion.

Where a handle is returned to represent the object and it is passed to
"member methods" that accept the object as a parameter.

Would it really be hard for IBM to put some syntactic sugar around that and
pass it off as OO.



-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of hr@xxxxxxxxxxxx
Sent: 20 April 2010 20:34
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Why use PHP? What are the disadvantages?

The hardest thing to understand in OO is the scope you are in and that
scopes executes asyncrone - like Nathan I wouldn't like RPGLE to have full
OO capabilities, there is no need for it.

/Henrik




Nathan Andelin <nandelin@xxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
20-04-2010 19:48
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Why use PHP? What are the disadvantages?

From: Neill Harper
So why isn't there a demand for OO RPG, I want it ;-)

I would REALLY prefer that IBM NOT make RPG a fully OO Language!
Procedural interfaces are better for a business oriented language, IMHO.

Notwithstanding the foregoing, Barbara Morris shared a little technique a
number of years ago, which I've used extensively. OO languages generally
use the "new" keyword to instantiate new objects, which encapsulate
properties and methods. As an alternative, consider doing something like
the following in RPG:

myPointer = myObjectNew();

Where myObjectNew() creates a new instance of a data structure, using
%alloc(), and returns a pointer to it. That data structure represents a
new instance of your object. All other procedures in the service program
reference a particular instance of that data structure via "myPointer".

For "inheritance" purposes, consider writing service programs which are
essentially wrappers around other service programs, but provide
successively higher levels of abstraction.

Forget "polymorphism", it's not worth it.

Just suggestions,

-Nathan.