• Subject: Re: IBM pushing Java
  • From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
  • Date: Sun, 28 Mar 99 16:23:39 +1100

Hello James,

Not a bad effort at all (in my not so humble opinion). See my append to Booth 
about some of your points.  The 
one I most wanted to discuss here was the DDS/record analogy.

I think a record can be visualised as an Entity therefore a record in a 
Customer Master file can be thought of 
as a Customer object.  In this case it is a fully populated Customer object.  
An empty record (INZPFM etc) 
would be like a shell Customer waiting to be populated.

The DDS for a file is more like the class definition (template) for a File 
object.  This class is instantiated 
via the CRTPF (or CRTLF etc) command.  In the same way RPG source is the class 
and CRTRPGPGM instantiates the 
class and gives us a Program object.

Who said the AS/400 isn't object oriented?  Yes, I know it's object-based but 
when CPF was designed OO WAS 
object based.  Inheritance, polymorphism, etc came later.

Simon Coulter.

 FlyByNight Software         AS/400 Technical Specialists       
 Eclipse the competition - run your business on an IBM AS/400.  
 Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           
 Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      
 Windoze should not be open at Warp speed.                      

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].