types and operators
Captain Napalm
spc@armigeron.com
Sat, 27 Apr 1996 06:30:29 -0400 (EDT)
A long long time ago on a network far far away, Eric W. Biederman thus said:
>
> One comment about frames & GC etc. I'm frustrated because I found a
> solution to a lot of things that wouldn't inconvinience a programmer
> in any other language but forth. Arrgh, we're working in forth!
>
Could you go into more detail about this?
> Yeah. C might be most useful if we can use it "as is", in an OTOP
> environment. But as we intend to do runtime code generation,
> GCC is out of question. And as utsl says, GCC isn't something you can
> extract a part from: by the time you manage to get something running,
> you could have rewritten it twice.
>
> Actually the innards of GCC aren't all that bad. The outards are
> terrible though.
Yes, but how do you extract the innards of GCC from the gunk that makes up
the outards? 8-)
> I'm willing to writa a GC routine that will handle everyhard case
> except trying to use DWIM to find the pointers.
>
Well, do the DWIM in the HLL then <duck>
-spc (Finally catching up on some email ... )