[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] USERDEF stack size

Vincent Rivière wrote:

Helmut Karlowski wrote:



So VDI_INTINMAX became larger?



Good question.
Maybe the old QED/CF-Lib binary was compiled with Pure C, which had different GEM bindings ? 


The standard Pure C gemlib uses parameter block and arrays globally
defined once.

Question is: who needs such a large array for v_gtext?
v_gtext is not a console output function, it does not wrap around
on screen. Any array larger than 1920/8 looks like monsense.
But then, even with intin[256] it might be too much for a USERDEF.
I had to make a static intin for v_gtext in AHCC's gemlib.

I think cutting off v_gtext input string at 80 would suffice.

Note also, that the whole parameterblock is defined locally on
the stack. Which is good and makes tuning per VDI call perfectly
possible.

--
Groeten; Regards.
Henk Robbers. http://members.chello.nl/h.robbers
Interactive disassembler: TT-Digger;  http://digger.atari.org
A Home Cooked C compiler:      AHCC;  http://ahcc.atari.org