× 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: Message not deliverable
  • From: "Bob Cozzi" <cozzi@xxxxxxxxx>
  • Date: Thu, 12 Aug 1999 13:19:21 -0500
  • Importance: Normal

Hans,

Doesn't PL/I allow this already? It has been a while, and I don't recall,
does PL/I have reserved names? That's the direction in which this train
should moving if I can't derail it.

Bob Cozzi

http://www.RPGIV.com




> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of Douglas Handy
> Sent: Wednesday, August 11, 1999 7:27 PM
> To: RPG400-L@midrange.com
> Subject: Re: CF-Spec - another call for opinions
>
>
> Bob,
>
> > I definitely want a vote AGAINST option 4!!!
>
> Hey, Bob, you found something we can agree on regarding CF!  Option 1
> would be (IMHO) much preferable than option 4.  I don't like option 3
> either, as it could lead to some unnatural future opcodes.
>
> I still like option 2 best, and think that implied EVAL and CALLP can
> be unambiguously determined from the context in almost every case.
>
> I think the only ambiguous context would be an implicit CALLP to a
> subprocedure with no agruments passed, where the name matched a
> current or future opcode with no operands.  (Such as Iter or Leave.)
> This is why I suggested appending () to ensure it would continue to
> always be recognized as a subprocedure call regardless of future
> opcodes.
>
> Note that new opcodes which require operands (i.e., almost every one)
> would still not be ambiguous since the presence/abscense of "=" vs
> operands vs arguments would allow you to easily determine if you are
> dealing with an opcode, target variable, or subprocedure name.
>
> Doug
> +---
> | 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


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