Vincent Rivière wrote:
Jo Even Skarstein wrote:This is exactly how traditional AES/VDI-bindings work. The downside is that such bindings won't be re-entrant.Really... Does QED need reentrant bindings ?
A program that does not need rentrancy because it doesnt use threads should be most comfortable with a few bindings using a static array. So dont worry. Let people writing multithreaded applications find the solution they need. OTH, I like the idee of XaAES setting up a userdef stack per application. Shouldnt be too difficult. The AES already needs application specific data. I wrote AHCM for that purpose, when XaAES itself was a usermode program. Switching to user mode looks like a good idee for the KM. -- 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