[Fowarded from pop-forum]
(In windows Poplog 15.5 -- I assume this hasn't changed recently)
The command "bye" is a macro (showlib bye, in a working poplog). It's
definition is:
define global macro bye;
"sysexit","(",")",";"
enddefine;
This suggests to me that the file lib/auto/bye.p is being loaded and
compiled correctly, and prompts two questions:
(a) What happens if you type the command
sysexit();
directly to the prompt? E.g.
Setpop
: sysexit();
and (b)
What happens if you type => to the prompt? What you should see is:
Setpop
: =>
**
:
If that works, try:
Setpop
: 2=>
which should print
** 2
so the console will look like
Setpop
: 2=>
** 2
:
Jonathan
----- Original Message -----
From: Philippe Roy
To: poplog-dev@cs.bham.ac.uk ; pop-forum@cs.bham.ac.uk
Sent: 11 January 2005 20:50
Subject: running "bye" on OS X
Hi! Great advances in the poplog port to OS X.
We now have it initializing, and the console is prompting for commands.
We do have a new problem.
When we type an instruction the system does not
execute it correctly, we are trying to figure out what is
happening, so we modified the function sysPUSHQ in
vm_plant.p in order to evaluate the "bye" instruction
by adding this line:
cucharout(\n'), printf (item, "sysPUSHQ": %P),
cucharout(`\n`);
And we also modified sysexit in sysexit.p by adding
this line:
cucharout(`\n`), printf('Entro a sysexit'),
cucharout(`\n`);
when we execute newpop11 on LINUX and type the command
"bye" on the console we have the following printing
result:
SyspushQ: sysexit
SyspushQ: (
SyspushQ: )
SyspushQ: ;
Entro a sysexit
And after that, it exits the application normally.
On OS X we get this results:
SyspushQ: sysexit
SyspushQ: (
SyspushQ: )
SyspushQ: ;
What should happen then is sysexit being called. We would
like to know what exactly should be called once these SyspushQ
are done.
thanks a lot for any help you can give us!
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
|