× 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.


  • Subject: RE: Thanks for nothing! (was THANKS!)
  • From: "Bob Cozzi" <cozzi@xxxxxxxxx>
  • Date: Thu, 12 Aug 1999 13:16:40 -0500
  • Cc: "one List" <RPGIV@xxxxxxxxxxx>
  • Importance: Normal

Great idea Hans!  Another horse-shit design by default in RPG IV.  Yeah, we
all love the colons, don't we? So because your original design choices don't
work in all situations, we end up with something no one "voted" for, but it
is the choice "most people wanted" will be your response.

THIS IS TYPICAL TORONTO "BAIT AND SWITCH"  Tell us we're going to get this
cool new feature, a few people buy into it and support the idea, then turn
around and change it.

I'm not sure which is more disheartening having the Speaker of the U.S.
House of Representatives as my congressman, or seeing RPG being designed to
its death.



Bob Cozzi

http://www.RPGIV.com




> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of boldt@ca.ibm.com
> Sent: Thursday, August 12, 1999 10:24 AM
> To: RPG400-L@midrange.com
> Subject: Thanks! (was: CF-Spec - another call for opinions)
>
>
>
>
> Thanks for your responses, everyone!  The discussion
> has been very useful for us, with some responses very
> close to what we've come up with.
>
> We've done a bit more brainstorming, and we think we've
> hit on another alternative that we think everyone will
> be happy with.  In a nutshell, we believe that we can
> achieve release to release compatibility with two
> changes to our design:
>
> 1) Require parens always on CALLP statements on the
>    CF-Spec; and
> 2) Delimit opcode extenders on the CF-Spec using some
>    different character other than parens, such as the
>    colon.
>
> Basically, if the first string of characters in the spec
> is followed by "(", it is either an EVAL or CALLP; by
> "=", it is an EVAL; otherwise, it is an opcode.
>
> So, here's what our toy example looks like:
>
>     CF KeepLooping = *ON
>     CF dow KeepLooping
>     CF    read:e MasterFile
>     CF    if %eof
>     CF       HandleEndOfFile()
>     CF    endif
>     CF enddo
>
> Cheers!  Hans
>
> Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com
>
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---END
>
>

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



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.