Ficl - small systems scripting with OO Activity
Brought to you by:
jsadler
I have not looked at FICL, so I don't know how it uses setjmp/longjump. In Gforth we use setjump/longjump to get back from the signal handler (for stuff like invalid memory access, Ctrl-C, stack underflow, division by zero) to the engine. All these conditions produce a Forth-level exception, which helps getting around the problem for gforth-fast (the benchmarking engine): All stack pointers and the instruction pointer are reset to the value stored in the exception frame, so if we lose the values...
New compilers (GCC >4) may not work