> O.K. - this is the reasonable behaviour and I think we should check for it > in the configure process. > > If it's not there, we might want to bring along a free implementation > in the long run.
IMO if it's going to be this much work to A) determine if snprintf is present, B) implement our own snprintf and C) actually figure out if the offered implementation is doing the right thing with the null terminators, or if it is an old crusty one that wasn't quite implemented right and noone ever noticed, we should just code around the whole problem and just rewrite things safely without using it. -- Brian
