svn commit: r202661 - head/lib/libc/gen

2010-01-19 Thread Ed Schouten
Author: ed Date: Tue Jan 19 23:07:12 2010 New Revision: 202661 URL: http://svn.freebsd.org/changeset/base/202661 Log: Revert r202447 by re-exposing the old uname(3) function. It makes hardly any sense to expose a symbol which should only be provided for binary compatibility, but it seems

Re: svn commit: r202661 - head/lib/libc/gen

2010-01-19 Thread Mark Linimon
Thank you. mcl ___ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to svn-src-all-unsubscr...@freebsd.org

Re: svn commit: r202661 - head/lib/libc/gen

2010-01-19 Thread Bruce Evans
On Tue, 19 Jan 2010, Ed Schouten wrote: Author: ed Date: Tue Jan 19 23:07:12 2010 New Revision: 202661 URL: http://svn.freebsd.org/changeset/base/202661 Log: Revert r202447 by re-exposing the old uname(3) function. It makes hardly any sense to expose a symbol which should only be provided

Re: svn commit: r202661 - head/lib/libc/gen

2010-01-19 Thread Ed Schouten
* Bruce Evans b...@optusnet.com.au wrote: Of course it is against standards. This is implicit for most functions, and the part of the standard that you quoted says it explicitly for uname(): | The following shall be declared as a function and may also be defined