Works ok up to 15 items on the stack. After that I get screwy results back.
I just changed the written word to a number and added a few more to the list. Here's what I get with a stack dump after the tokenizer: 1<--- save .... all ok 30 <-- save restore --> 30 restore --> 29 restore --> 28 restore --> 27 restore --> 26 restore --> 25 restore --> 24 restore --> 23 restore --> 22 restore --> 21 restore --> 20 restore --> 19 restore --> 30 restore --> ; restore --> ; restore --> ; restore --> restore --> restore --> restore --> restore --> restore --> restore --> 2 restore --> 20 restore --> 19 restore --> 9;20;21;22;23;24;25;26;27;28;29;30 restore --> 3 restore --> 29 restore --> 28 restore --> 8;29;30 --josh ----- Original Message ----- From: "Bryan C. Warnock" <[EMAIL PROTECTED]> To: "Clinton A. Pierce" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 8:43 AM Subject: Re: Problems with strings on the stack (small, concise example) > On Friday 22 March 2002 08:22, Clinton A. Pierce wrote: > > Some patches committed last evening nearly took care of the problem -- at > > least they appeared to make my small example appear to > > work. Sometimes. :) Here's a slightly larger but better example that so > > far hasn't failed to show the stack corruption problem anywhere: > > Here's my output: > > Whammo 26> parrot clint2.pbc > one<-- save ( ;boundary) > two<-- save ( ;boundary) > three<-- save ( ;boundary) > four<-- save ( ;boundary) > five<-- save ( ;boundary) > six<-- save ( ;boundary) > seven<-- save ( ;boundary) > eight<-- save ( ;boundary) > nine<-- save ( ;boundary) > ten<-- save ( ;boundary) > eleven<--saved (endproc) > > -- > Bryan C. Warnock > [EMAIL PROTECTED] >
