"Peter Hunnisett" <[EMAIL PROTECTED]> writes:

> Sounds like it should be using something like vsnprintf internally.
> 
> If no one has any objections to changing the use of vsprintf to vsnprintf
> I'll do something up and submit it.

vsnprintf is not available everywhere, so yes I do object. I don't see
any good reason for displaying more than 500 bytes of debugging output
in a single call anyway; code that does this is broken. Dumping
unknown strings should be done with the debugstr functions, which will
limit the size to something reasonable.

-- 
Alexandre Julliard
[EMAIL PROTECTED]

Reply via email to