cvs commit: src/include string.h src/lib/libc/string Makefile.inc memchr.3 memrchr.c src/sys/sys param.h

[Maxim Sobolev]

David Schultz wrote:

> ISTR that in prior discussions on symbol versioning, the consensus
> was that there's nothing wrong with adding new APIs in -STABLE
> branches, but of course apps that use the new features won't be
> backwards-compatible.
> 
> By the way, one catch is that once you MFC symbols in the FBSD_1.1
> namespace, any new symbols in the same library need to go in
> FBSD_1.2. We do guarantee that public namespaces do not change
> across stable branches. This is important for API-checking tools
> like appcert: even if you can't prevent problems like the one
> described previously, at least you have some assurance as to which
> versions of FreeBSD will run your app.

Interesting. It's not very clear, though. Are you saying that in this 
case memrchr will be in different namespace than the rest of 6.4 libc 
functions?

-Maxim