On Thursday 12 November 2009 14:08:29 Bernhard Reutner-Fischer wrote: > Signed-off-by: Mike Frysinger <vap...@gentoo.org> > Signed-off-by: Bernhard Reutner-Fischer <rep.dot....@gmail.com> > --- > include/stdlib.h | 2 -- > libc/stdlib/realpath.c | 20 ++++++++------------ > 2 files changed, 8 insertions(+), 14 deletions(-) > > diff --git a/include/stdlib.h b/include/stdlib.h > index e462c1c..3e9ceab 100644 > --- a/include/stdlib.h > +++ b/include/stdlib.h > @@ -659,7 +659,6 @@ extern char *canonicalize_file_name (__const char > *__name) __THROW __nonnull ((1)) __wur; > #endif > > -#if defined __USE_BSD || defined __USE_XOPEN_EXTENDED > /* Return the canonical absolute name of file NAME. If RESOLVED is > null, the result is malloc'd; otherwise, if the canonical name is > PATH_MAX chars or more, returns null with `errno' set to > @@ -668,7 +667,6 @@ extern char *canonicalize_file_name (__const char > *__name) /* we choose to handle __resolved==NULL as crash :) */ > extern char *realpath (__const char *__restrict __name, > char *__restrict __resolved) __THROW __wur > __nonnull((2)); > -#endif
Why is the __nonnull(2) still there? Isn't the point of this to ensure that the second argument _can_ be null? Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds _______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
