3 ms·
Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no?
by teacup50 10y ago
Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no?
- Manishearth 10y agoNot necessarily. I suspect even in the case of 2.0, most if not all of those apis will survive. Deprecation markers exist to encourage people to use newer, better APIs. I suspect that even if 2.0 happened, the only apis that would be removed would be ones that we're reasonably sure nobody uses (via crater), and even then there would be debate. And like Gankro said, 2.0 is a thing that's not supposed to happen in the first place.
- pcwalton 10y ago> Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no? No! That would be a basic violation of the compatibility promise that we've upheld since 1.0. Are you going to criticize C for marking gets() as deprecated?
- fanf2 10y agoC11 does not have gets() anymore!
- SamReidHughes 10y agoSorry, C will never live it down.