Robert Spier wrote:
>
> > > The HLL doesn't know, how many ops one source line will need.
> >
> > Not *normally*, but if it's including code which is already literal
> > assembler, it does: Imagine a version of lex/yacc wherein the the
> > blocks of code you give are imcc or pasm (instead of C). Clearly,
> > there's one op per line of source.
>
> Insert optimizer here.
Blech.
For that matter, won't the optomizer wreak havoc with other all of the
various other uses of .setline?
Anyway, how about this semantic: .setline_i would associate an
increasing series of line numbers to the ops which follow it, as if each
one had been preceded by it's own individiual .setline.
Thus, whatever solution we come up with for the optomizer's interactions
with regular .setline automagically applies to .setline_i, too.
--
$a=24;split//,240513;s/\B/ => /for@@=qw(ac ab bc ba cb ca
);{push(@b,$a),($a-=6)^=1 for 2..$a/6x--$|;print "[EMAIL PROTECTED]
]\n";((6<=($a-=6))?$a+=$_[$a%6]-$a%6:($a=pop @b))&&redo;}
