× 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: ILE Fear/Design (Was: Looking into the Program stack)
  • From: Anton Gombkötö <Gombkoetoe@xxxxxxxxxx>
  • Date: Wed, 5 Apr 2000 12:22:07 +0200

Dear István,

a) reminds me somehow of searching an RPG expert, max. 20 years old, with 30
years of experience.

b) The first finger loads the program, following fingers only get their own
variable storage. But that's how i suppose the machine does it already with
every program.
The so-called OPM CALL does still exist; it's just the "dynamic" call. And
this isn't forbidden or old style. The worst thing i can imagine is binding
all these F4-programs to every program!
The call of a matchcode-program or the callp of a matchcode service program
are pretty much the same; i assume the first one to do more harm to storage
/ performance. The compiler knows much more about the function/procedure to
be called at compile time and might be able to optimize it. If not now,
maybe in coming releases. CALLP offers other advantages, but you'll read
this in the re(a)dbook...

But maybe the experts can explain this for us? Hans?

:-)

--
Anton Gombkötö


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