...> #define push(s) ((void)(((stackptr = (stack + stacksize)) ? growstack() : (void)0), (*stackptr++ = errcheck(s)))) ...? void push(Whatever *s) { if(stackptr = stack + stacksize) growstack(); *stackptr++ = errcheck(s) } this eliminates two ...#define push(s)\ do {\ if(stackptr = stack + stacksize)\ growstack;\ *stackptr++ = errcheck(s);\ } while(0) but ...

..., at 9:53 AM, Pietro Gagliardi wrote: Hello. I have a simple push macro for a stack machine interpreter. It looks like this: #define push(s) ((void)(((stackptr = (stack + stacksize)) ? growstack() : (void)0), (*stackptr++ = errcheck(s)))) Does this boggle the mind? It's very simple: it checks for stack overflow and makes the stack bigger if so, then checks to see ...

Hello. I have a simple push macro for a stack machine interpreter. It looks like this: #define push(s) ((void)(((stackptr = (stack + stacksize)) ? growstack() : (void)0), (*stackptr++ = errcheck(s)))) Does this boggle the mind? It's very simple: it checks for stack overflow and makes the stack bigger if so, then checks to see if s, a double, is NaN or ±Inf, and finally pushes ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...

... to 65536 or more. The default should be fine, and can be changed at runtime with Coro::State::cctx_stacksize. C stack size factor? [16384] 16384 using a stacksize of 16384 * sizeof(long) *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Coro can optionally put a guard area before each stack segment. When the stack is too small and the access is not too far ...