• Subject: Re: RPG vs. C
  • From: John Hall <jhall@xxxxxxxxxxx>
  • Date: Mon, 11 May 1998 09:17:29 -0400
  • Organization: Home Sales Co.

Kris Ball wrote:
> > IMHO, it's too hard to write APPLICATIONS in C... you have to do far too
> > much work to accomplish the same thing you can do in a few lines of code in
> > RPG.
> I agree.  I took a C class, and one of the programs we wrote was to delete a
> record from a file.  Hello?  I can program that function in 1 line of code in
> RPG.   But it is valuable for me to explore other languages and expand the 
> old programming methods I sometimes fall back on.
> So now I'm learning Java, and what do you know?  Those C classes were a good 
> after all!
> --

You guys crack me up !!  (all of you - not just Kris)

  If you took a poll of 100 C/C++ programmers who had taken one course
in RPG how many do you think would say "RPG is the better language" ??  
Each language has its relative strengths & weaknesses.  
Sure there are things in C which take many more lines of code than in
RPG (Delete is not one of them though).  But on the other hand large
sophisticated logic programs are easier to write in C. RPG still lacks
variable scope and type definitions.  The service module concept
attempts to address scope and code reuseability but it is still a bit of
a kludge.

Thanks to ILE you can now use each one where it is most appropriate.  

Putting on my Nomex flame proof suit now .....

John Hall
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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].