><<Place any old number between 1 and 5 into column 0.>> > >but column 0 is for A, not a temp variable. I got the impression that the problem is that do has to create temp variables and they get overwritten (or something along those lines). Why not then specify a range of variable numbers that can only be used by do? That or just append it to the table instead of putting it in the temp space? I think do and send are vital to OpenCard, we just saw a huge backlash against Serf on the HC list because Dan wouldn't implement do. People want do, we should give it to them. It's obviously possible because HC did it and so does MetaCard (MetaCard notes that do statements could take up to 30 times longer than normal statements). Adrian Sutton.
- OODL: Runtime Code Generation: Almost as evil as the secan... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as evil as ... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almost as evil... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as ... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almost... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as evil as... MP0werd
- Re: OODL: Runtime Code Generation: Almost as evil as... Paul Sutton
- Re: OODL: Runtime Code Generation: Almost as evi... DeRobertis
- Re: OODL: Runtime Code Generation: Almost as... M. Uli Kusterer
- Re: OODL: Runtime Code Generation: Almos... DeRobertis
- Re: Re: Re: OODL: Runtime Code Generation: Almost ... MP0werd
- Re: Re: Re: OODL: Runtime Code Generation: Almost ... MP0werd
