The stack opcodes for a, k, i, and S types should not be very hard
to implement, so it may be possible to have them already in 5.02 if
they are found to be useful.

On Thursday 04 May 2006 15:48, David Akbari wrote:

> I, for one certainly like the sound of this - it reminds me of the 
> things I like about using SC3. This would likely also work toward 
> unifying the Subinstr and UDO idea into a more coherent whole, under 
> the hood.
> 
> Of course, a change of the magnitude suggested would hopefully coincide 
> with a release of version increment 5.03, as the 5.02 release date is 
> approaching rapidly and there are already a ton of new and exciting 
> frontends etc that should be out and available to the public to use 
> that arguably should take precedence over the exciting changes 
> suggested in the previous email.
>
> -David
> 
> ps. new\n parser\n parser\n parser\n ;)

Not sure if it would help much here, as the limitation is not on the
syntax level.