Re: [MiNT] USERDEF stack size

[arnaud.bercegeay@free.fr]

Hello,

> Do everybody agree to replace the above lines by malloc(), everywhere
> in 
> the GemLib where VDI_INTINMAX and VDI_INTOUTMAX are used ?

I'm not sure it's a good idea : please keep in mind that gemlib is not only used to build GEM applications (like QED for example). Gemlib is also used to build "binaries" that are not GEM applications.

For example, it may be used to build the AES itself (MyAES, XaAES...), and i'm not sure that standard libc malloc() is a good idea here.

Another example : some "shared" libraries use gemlib, and once again, libc-malloc() is not a good idea at all.

Another point against malloc() : a lot of optimizations have been done by several contributors in gemlib in order to speed-up gemlib, and this general modification (add one malloc() and one free() in a lot of VDI functions) may kills gemlib performances... but maybe these optimizations are no more so useful because we all have powerful computers now...

Arnaud.