× 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: Is this the Free-Format that we asked for?
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 06 Nov 2000 08:23:28 -0800
  • Organization: Pacer International

Well, I don't use LEAVE very much, but I have.  I do not like it,
but, when I see a LEAVE I know exactly what it's doing and where
it's going, and it can only go DOWN, not UP.  I think it should
be kept in.

Regards,

Jim Langston

Carel Teijgeler wrote:
> 
> Jon.Paris@hal.it wrote:
> 
> > Not true - I don't like Leave or LeaveSr either but at least they have the
> > benefit of having a language defined target - not one that can be moved
> > virtually anywhere in the code!
> >
> 
> Jon,
> 
> I do not agree with you on that. LEAVE jumps to the first END(DO) in the same
> subroutine. LEAVESR is like GOTO: it can jump to anywhere in a programme, 
>because
> a subroutine can be called from anywhere in a programme.
> 
> If IBM intents to drop GOTO, they should also drop LEAVESR.
> 
> Carel Teijgeler
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.