thanks for response ;) i was a little bit nerved and thougt why does ncurses put all its data on the stack.... (i found that out trying a clearstack und then trying to write something to the screen... it doesnt work)...
sorry i have no knowlegde of C so i cant fully understand what the c linker does or does not... and what a callback is... but will try to rename the global variable in the named files ;) > Yep, found it. ncurses messes around with the global variable SP, which > we define and use to store the stack pointer while calling a C function > (we need it be a global variable, since callbacks need to know the > Forth stack pointer). > > Renaming that global variable to SPg (for SP global) cures the problem. > > SP is defined in engine/main.c, and used in prim and engine/engine.c. > It's declaired in engine/forth.h. All these locations have to be > changed. > > libncurses brings its own SP, but since Gforth is compiled to export its > own symbols (so you can create a library that calls back), the C linker > is confused. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
