× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. August 2003

Re: v4 vs v5 rpg. was Prototypes, /COPY and LIKE()

Steve Richter wrote: 
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Buck
Sent: Wednesday, August 13, 2003 11:49 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Prototypes, /COPY and LIKE()



You have to get a laugh at the hypocracy of IBM however.
On the one hand they say that RPG is dead,



Citation, please?  I have never heard IBM say RPG is dead; exactly the
opposite.
--buck



You cite first!  Because of the conspiracy, there will not be any IBMers on
the record stating that RPG is history.

A proc centered rpg makes features like a static free rpg very doable. Once
rpg or its derivative is static free, then the language can be thread
capable, can handle exceptions better, ...  The point being that there are a
lot of ways that rpg can be improved.  Yet, there are no v4 to v5 like
improvements planned.

What is the current year IBM r/d budget for rpg? what was it 5 yrs ago?

Huh?

(rubs eyes in disbelief)

LOL!

This is hilarious! So a possible reduced rate of RPG enhancements means RPG is dead? So we not only have to continue to enhance the language, but do so at an *increased rate* to demonstrate that RPG is not dead?

Thanks Steve, you really made my day!

Cheers! Hans



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.