3 ms·
Exactly. While they can't fix the old functions without potentially breaking software that relied on the old behavior, they can introduce a new set of process-
by JoshTriplett 10y ago
Exactly. While they can't fix the old functions without potentially breaking software that relied on the old behavior, they can introduce a new set of process-launching functions that do the right thing: handle arguments exactly as written, no splitting, no quoting, no metacharacter interpretation.
Then, for new OSes, write a compatibility layer to implement the old functions on top of the new ones, and for old OSes, write a compatibility library to implement the new functions by quoting and passing to the old ones.
Mark the old functions as "deprecated, do not use in new code", and point to the new ones.
- gravypod 10y agoThis is something that is important. The steps to go about. 1. Fix old solution 2. Implement alternative that is feature complete and document 3. Write comparability layers If people followed this life as a software developer would be easier on bloodpressure. I remember fondly working with many APIs thst were deprecated but had no alternative and the devs admitted it.