On 10/15/07, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> The only thing which broke my old code regarding switching to vsnprintf
> is that old Ns_DStringPrintf handled empty string differently, vsnprintf
> now puts (null), before that empty string did not put anything.
>
> I still need to review si the damage is critical enough or never upgrade
> until all code updated. That sucks
The printf familly calls make no guarantee about NULLs. If we're
relying on that anywhere in the code it's a bug and we need to fix it.
e.g.:
Ns_Log(Warning, "huh?: %s", nullable ? nullable : "uh-oh");
Otherwise, we can expect crashes.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
