> Now, the other issue is what to do about allocating memory. Alexandre > mentioned that NT has a per-thread buffer that it uses. That is probably > the way to go, since it's allocated ahead of time if you get an OOM error on > that, you have other issues. You of course also need to deal with growing > and shrinking the buffer to accomodate very large strings. I just like to mention this buffer is only used by low level-dll's (found references from advapi32 and ntdll mainly) and it looks like we can use it only for functions not calling further into any of these native dlls - or better: not to call any other function internally We would need to use the stack or (the same) alloca. ciao juergen --- [EMAIL PROTECTED] ... from sunny Berlin
- Re: More on the ASCII/Unicode support Dimitrie O. Paun
- RE: More on the ASCII/Unicode support Patrik Stridvall
- Re: More on the ASCII/Unicode support Alexandre Julliard
- RE: More on the ASCII/Unicode support Patrik Stridvall
- Re: More on the ASCII/Unicode support Alexandre Julliard
- Re: More on the ASCII/Unicode support James Sutherland
- RE: More on the ASCII/Unicode support Patrik Stridvall
- RE: More on the ASCII/Unicode support Patrik Stridvall
- Re: More on the ASCII/Unicode support Alexandre Julliard
- Re: More on the ASCII/Unicode support David Elliott
- RE: More on the ASCII/Unicode support Juergen Schmied
- RE: More on the ASCII/Unicode support Patrik Stridvall
- Re: More on the ASCII/Unicode support David Elliott
- Re: More on the ASCII/Unicode support Dimitrie O. Paun
- Re: More on the ASCII/Unicode support gerard patel
- Re: More on the ASCII/Unicode support gerard patel