On Tuesday 11 June 2013, André Malo wrote: > > trunk patch: http://svn.apache.org/r1491155 > > 2.4.x patch: trunk patch works > > nd: why would you do that in a stable branch? > > > > + sf: Because it is only annoying and serves no purpose > > anymore. If you + want, we can make it a minor MMN bump > > for adding a "new" API. +1: sf, covener > > > > -1: nd > > Long discussions in STATUS are kinda tedious ;-) > > Well, I think, such changes are what trunk is for. Why not simply > leave everything below as-is? Even more if it removes only an > annoyance? Or is there a real technical reason I'm just not seeing > right now?
It is a useful function. Disallowing it breaks ISO-C compliant code for no good reason. There has been a complaint by a module author. Allowing it does not use any memory because the function is already in libc. Working around the missing function requires additional code, which uses memory and may contain bugs. What more reasons do you need? Or, is there a real technical reason to keep it broken in 2.4?
