> This sort of interface, combined with implementing printf()'s as
> an sfront-specific SAOL construct (like idump and kdump are
> saolc-specific constructs), should bring debugging SAOL out
> of the stone age.
One thing that I do like about how 'saolc' does its "dump" is to allow
control as to when these things happen. Or do you think it might be more
simple (read "elegant") if sfront were to determine the "rate" of the
printf() from the parameters? Or do you see a need for 'iprintf()',
'kprintf(), etc...?
Anyway, I did figure that there was some "magic" you had up your selve,
but you are also very intimate with sfront and what is going on inside.
Thanks,
Mike
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:03:53 EST