At 4:36 PM + 3/19/02, Leon Brocard wrote:
>Clinton A. Pierce sent the following bits through the ether:
>
>> Actually, if I knew where to look I'd update them myself. :)
>
>http://parrotcode.org/examples/ mentions them but I guess we should
>roll the ideas behind:
>http:[EMAIL PROTECTED]/msg
Clinton A. Pierce sent the following bits through the ether:
> Actually, if I knew where to look I'd update them myself. :)
http://parrotcode.org/examples/ mentions them but I guess we should
roll the ideas behind:
http:[EMAIL PROTECTED]/msg06001.html
into one of the files in docs/...
Leon
--
At 11:24 AM 3/19/2002 -0500, Dan Sugalski wrote:
>At 11:15 AM -0500 3/19/02, Clinton A. Pierce wrote:
>>
>>What follows are a collection of PASM routines that I've been using while
>>tinkering with the assembler and parrot. Feel free to use, mutilate, add
>>to, discuss, mock. They are:
>
>Thes
At 11:15 AM -0500 3/19/02, Clinton A. Pierce wrote:
>
>What follows are a collection of PASM routines that I've been using
>while tinkering with the assembler and parrot. Feel free to use,
>mutilate, add to, discuss, mock. They are:
These are cool, and thank you very much. Mind if I update th
What follows are a collection of PASM routines that I've been using while
tinkering with the assembler and parrot. Feel free to use, mutilate, add
to, discuss, mock. They are:
a tokenizer
isalpha and isspace
stack routines: sort, replace, peek, reverse
a sta
