|
Hi John,
I more or less agree with you.
But, does it make sense for IBM to develop features aimed at the RPG/400 programmer (or RPG IV programmer who codes RPG IV exactly as he did RPG/400)???
Those people aren't using the new features anyway! So creating more functionality aimed at them is a waste of time.
john e wrote:
Ok, maybe i encountered two, in my 20 yrs of RPG experience...
But i encountered many on this forum with (some) OO knowledge, or programming knowledge / interest in general.
This forum is in no way representative of RPG programmers.
I suppose that every knowledgable RPG programmer (i.e. is interested in programming in general) reads this forum.
The programming knowledge / interest of the average RPG programmer is embarrassing...
Date: Tue, 12 Jan 2010 09:07:47 -0600_________________________________________________________________
From: vhamberg@xxxxxxxxxxx
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: RPGV?
John
You have encountered one now - who has known of that stuff for years.
;-)
john e wrote:
Namespaces / overloading has nothing to do with OO.-snip-
OO is all about encapsulation.
You don't encapsulate anything with namespaces/overloading.
OORPG... please
First try to make the current version of RPG a bit more sane...
And why bother, i never encountered an RPG programmer who even heard about terms like "encapsulation" or even "variable scoping", let alone use it.
--
This is the RPG programming on the IBM i / System i (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.
Het laatste nieuws, shownieuws en voetbalnieuws op MSN.nl
http://nl.msn.com/
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.