Re: Tru64, snprintf and bug #1298

First of all the internal replacement of snprintf fails if size is 1 or 0. Second it is not C99 complient and third we do not include it the right way. We would need to check if snprintf is available and if it is C99 complient and if not use the replacement. I had a lengthy discussion with the php group on that but i did not get any answer at last. This might be the case because my first worst assumptions were wrong for most systems. In fact i could commit detection code and corect replacement code but will do only when receiving a go from the group. regards marcus At 23:31 16.08.2002, Dan Kalowsky wrote:

Yes, that is correct, bug #1298 (it's existed for a LONG time). The user is having some difficulty compiling the Zend libraries for 4.2.2. Mainly it seems that snprintf is turning up as an unresolved symbol. I asked him to grep through the /usr/include looking for it, and the result was nothing. Looking through the code I see PHP has it's own snprintf implementation, and that should suffice. Apparently zend_API.c though doesn't notice it. His fix was to place <#include "php.h"> inside the file, and everything worked fine. Does anyone have any more insight into this that they might be able to share? ---------------------------------------------------------------<

Dan Kalowsky                    "A little less conversation,

http://www.deadmime.org/~dank a little more action."

dank-nom@aps-deadmime.org       - "A Little Less Conversation",
kalowsky@php.net                        Elvis Presley

-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php