Re: A86: Parameters (was A86: Personal Intro & Questions (fwd))
[Prev][Next][Index][Thread]
Re: A86: Parameters (was A86: Personal Intro & Questions (fwd))
Can someone write a tutorial on this parsing stuff? asap is some sort of
user token, does that mean you can create your own like TI-OS command? Like
beep( could create a beep? Is that way this parameters are mentioned? Like a
beep(10, 100) could make a ten second beep with a 1000 hz frequency. What's
going on here! :-) Sounds cool. Why would TI creates all these conveniences
for programmers yet not document them. Pat seems to document the TI-83
fairly nicely, does the TI-83 make more money then the 86 or has pat gotten
tired of writing up documentation?
Oh, and what is this EOS stuff? I am struggling to keep up with the mailing
list...
Later,
Matt
>Great! Nice job. :-)
>So we can just use pop and rst 10h then, eh?
>
>Stephen Hicks wrote:
>>
>> Ok... I made a quick test program (actually, i modified a test of
asapasm by typing in the
>> hex in the emu after the code started running) and i found out the
following:
>>
>> When a parameters are passed, the parser starts with the first parameter.
It checks if it is
>> a real (either variable or literal). If it's a real number, then it
pushes the real number
>> onto the FPS. If it's not, it checks if it's a variable or a literal.
If it is a variable,
>> it pushes the variable info (VAT entry) onto the FPS. Otherwise, if it
is a literal, it
>> creates a temporary $xx variable (which is deleted after the code is
executed) and pushes the
>> new $xx variable's VAT entry onto the stack. This is done for all but
the last parameter,
>> which is just loaded into OP1, but not pushed.
>>
>> Stephen Hicks wrote:
>>
>> > pushed; if it is a non-real type, the variable name is pushed. I am
going to test this
>> > today.
>>
>> --
>> Stephen Hicks
>> mailto:shicks@mindspring.com
>> ICQ:5453914
>> IRC/AIM:Kupopo
>> Hopemage:http://www.mindspring.com/~shicks/
Follow-Ups: