Re: Call a external program from a program
- From: "John H Meyers" <jhmeyers@xxxxxxxxxxxxxx>
- Date: Mon, 01 Jun 2009 12:24:09 -0500
On Sun, 31 May 2009 19:43:05 -0500, NEDM64 wrote:
\<< KRAFT \>> doesn't executes KRAFT, but gives me 'KRAFT'
Then there is no variable named 'KRAFT' in the current or any higher
calculator directory, in which case the evaluation of the name
leaves the name on the stack.
The 48G series owners manuals have very good explanations
of how everything is evaluated;
I know less about the 49/50 series manuals,
because they were not as inspiring to read :)
If by any chance KRAFT is a command in a library,
that you may have installed after entering your own program,
then just edit your program again (make no changes,
just press ENTER after you start editing).
Each time you complete a UserRPL editing session,
the text that you were editing is automatically
recompiled into a binary program.
During compilation, an unknown word such as KRAFT is searched for
in the current and higher directories, and if not found,
it is searched for in attached libraries (including built-ins).
If the word is found first in a directory, the word is compiled
as a variable name; if the word is found first in a library,
it is compiled as either a library command or internal command;
if the word is not found at all, it is compiled as a variable name.
When the program is decompiled (displayed or being edited),
the word KRAFT looks the same in all cases, but if it got compiled
as a variable name, its evaluation can only evaluate a variable,
whereas if it got compiled as a command (or library command),
it can only execute that command.
One may therefore sometimes need to recompile UserRPL,
to cause the compiler to recognize a newly installed
(or newly attached) library.
No such confusion occurs in SysRPL, where there is a specific unique syntax
for each different type of object, e.g. "ID X" for a "global" variable name.
"LAM X" for a "local" variable name, "ROMPTR mmm nnn" for a library reference,
"PTR nnnnn" for a direct ROM address, etc.
[r->] [OFF]
.
- Follow-Ups:
- Re: Call a external program from a program
- From: Horszowski
- Re: Call a external program from a program
- References:
- Call a external program from a program
- From: NEDM64
- Re: Call a external program from a program
- From: John H Meyers
- Re: Call a external program from a program
- From: NEDM64
- Call a external program from a program
- Prev by Date: Thank you: HP-75D - How to separate "computer" from pod?
- Next by Date: Re: How to view vars without pressing the button???
- Previous by thread: Re: Call a external program from a program
- Next by thread: Re: Call a external program from a program
- Index(es):
Relevant Pages
|