Date: Fri, 19 Aug 2016 19:24:36 +0430 From: mokhi <mokhi64@gmail.com> To: kang joni <kangjoni76@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: how did BSD libc make binary compatibility promise beetween freebsd version? Message-ID: <CAByVWPUX4UY=iiHa%2BhmpDDBYA6HFFTRC=YcbgKC1Oi1_AXYj_w@mail.gmail.com> In-Reply-To: <CAOmy0w%2BVhaT5TVe%2BhFP04MkJj8X0OUo57OVOe7KQbzYGP7ZWBw@mail.gmail.com> References: <CAOmy0w%2BVhaT5TVe%2BhFP04MkJj8X0OUo57OVOe7KQbzYGP7ZWBw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If you mean using libc/libc++ API in FreeBSD with no break, This is what FreeBSD provides by symbol versioning to provide same/compatible API in different versions. This means If you have a program that uses an API [printf(3) for example] on FreeBSD 9, and a change made on that API in FreeBSD 10, you can be sure that change is compatible and doesn't break what you had expected till now. This is being implemented using symbol versioning. I'm not sure that i understand your question correct :) This is my answer to my interpretation of your question ;) [and also based on my interpretation of FreeBSD's behaviors and codes :D] Also as a side-note i guess freebsd-current@ is more helpful for you question's answer. Best regards, Mokhi.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAByVWPUX4UY=iiHa%2BhmpDDBYA6HFFTRC=YcbgKC1Oi1_AXYj_w>