|
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, October 19, 2007 10:21 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: Objects and such
I think, though, that sometimes we get blinded by
terminology. The idea of polymorphism is really pretty
simple, and we do it all the time, especially on the System i:
DLTF, DLTCMD, DLTPGM
If you think of these in object terms, they're really:
F.DLT, CMD.DLT, PGM.DLT
That is, you're sending the "DLT" message to the "F" object.
Move to the world of lower case and no abbreviations and you get:
File.delete, Command.delete, Program.delete
What does this say? It actually says two things. First, it
says that for each of these object types (or "classes" in
Java terminology) there is a delete method that can be
called. Different things will happen depending on which
object type you're deleting.
More importantly, though, it says that you can delete an
object represented by the File class by executing its delete
method, and that you can do the same for Command and for
Program. So finally:
myFile.delete(), myCommand.delete(), myProgram.delete()
This is the essence of polymorphism: call the same method for
different objects and the underlying code will do what it's
supposed to do.
To me, it's less an issue of understanding the concept than
it is of the syntax.
DLTCMD CMD(MYCMD) vs. myCommand.delete()
Joe
--
This is the RPG programming on the AS400 / 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.
As an Amazon Associate we earn from qualifying purchases.
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.