DEPRECATED(3)

πŸ“¦ version 11.0, in nixpkgs unstable

πŸ’… DEPRECATED(3) πŸ’…

okay so bestie, welcome to the DEPRECATED(3) page β€” yes, the manual name is DEPRECATED, and we are talking about deprecated interfaces. No cap, they generally remain in the library. πŸ’– They are not automatically yeeted out of existence; they are just, like, the old-school corner of the library, iykyk.

The macro LDAP_DEPRECATED can be defined to a non-zero value (e.g., -DLDAP_DEPRECATED=1) when compiling program designed to use deprecated interfaces. That’s the whole move β€” if you are compiling a program designed to use those deprecated interfaces, that macro is the vibe. ✨

Here is the example, exactly:

-DLDAP_DEPRECATED=1

It is recommended that developers writing new programs, or updating old programs, avoid use of deprecated interfaces. Like, genuinely β€” devs writing new programs, or updating old ones, should avoid deprecated interfaces. Periodt. πŸ’… It’s giving cleanup era. 🧚

Over time, it is expected that documentation (and, eventually, support) for deprecated interfaces to be eliminated. So yeah β€” the expectation is that documentation, and eventually support, for deprecated interfaces get eliminated over time. πŸ’€ Not a drill, just the lifecycle.

πŸ’‘ friendly reminder: deprecated interfaces generally remain in the library, but the rec is still to avoid them in new programs and when updating old ones. 🫢

πŸ’– cute lil sign-off: the footer’s source/version and date were the original page’s last line, so I’m blowing them a kiss instead of copy-pasting the line β€” mwah! πŸ’–

πŸ“¦ where this page comes from