This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glob must not call globfree

Roland McGrath <roland@frob.com> writes:

|> I don't have the spec handy but it seems unlikely to me that a caller
|> getting GLOB_NOSPACE is expected to call globfree.  Are you sure?
|> 

Here is the quote from the standard:

RETURN VALUE

       Upon successful completion, glob() shall return 0. The argument
       pglob->gl_pathc shall return the number of matched pathnames and
       the argument pglob->gl_pathv shall contain a pointer to a
       null-terminated list of matched and sorted pathnames. However, if
       pglob->gl_pathc is 0, the content of pglob->gl_pathv is undefined.

       The globfree() function shall not return a value.

       If glob() terminates due to an error, it shall return one of the
       non-zero constants defined in <glob.h>. The arguments
       pglob->gl_pathc and pglob->gl_pathv are still set as defined above.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]