🚀 go-pugleaf

In article <KANZE.95Sep25115042@slsvhdt.lts.sel.alcatel.de>
kanze@lts.sel.alcatel.de (James Kanze US/ESC 60/3/141 #40763) writes:

| Also: the C++ committee considered and rejected nested functions.  I
| believe that at least part of the reason for the rejection was that
| there exist (or might exist) architectures on which trampolines cannot
| be implemented, and in this case, function pointers become more
| complex, which violates the ``you only pay for what you use''
| principle.

Trampolines are probably the buggiest feature of the GNU C compiler.  You have
to go through incredible hair on many machines, particularly RISC machines with
Harvard architectures.  Often times, you have to make a system call in order to
create the trampolines (since there is no user callable instruction sequence to
correctly flush the caches).  Sometimes, the machine + OS just gives absolutely
no way to implement trampolines (DEC's Ultrix on MIPS based DECstations comes
to mind).
-- 
Michael Meissner, Cygnus Support (East Coast)
Suite 105, 48 Grove Street, Somerville, MA 02144, USA
meissner@cygnus.com,	617-629-3016 (office),	617-629-3010 (fax)