Re: [hackers] [sbase] [PATCH] libutil: Rename functions in reserved namespace to prevent potential conflict

2019-05-21 Thread Quentin Rameau
> strsep is reserved. > > C11 standard section 7.30 Future library directions: > > The following names are grouped under individual headers for > convenience. All external names described below are reserved no matter > what headers are included by the program. > > 7.30.10 String handling > >

Re: [hackers] [sbase] [PATCH] libutil: Rename functions in reserved namespace to prevent potential conflict

2019-05-21 Thread Evan Gates
On Tue, May 21, 2019 at 10:17 AM Quentin Rameau wrote: > x* is not a reserved namespace, nor is strsep. strsep is reserved. C11 standard section 7.30 Future library directions: The following names are grouped under individual headers for convenience. All external names described below are

Re: [hackers] [sbase] [PATCH] libutil: Rename functions in reserved namespace to prevent potential conflict

2019-05-21 Thread Quentin Rameau
> libc may define functions with the same names, but differing in prototype. > --- > Anyone have any comments on this patch before I push it? > > The motivating conflict is with strsep, which glibc declares as > > char *strsep(char **restrict, const char *restrict); > > which is not

[hackers] [sbase] [PATCH] libutil: Rename functions in reserved namespace to prevent potential conflict

2019-05-21 Thread Michael Forney
libc may define functions with the same names, but differing in prototype. --- Anyone have any comments on this patch before I push it? The motivating conflict is with strsep, which glibc declares as char *strsep(char **restrict, const char *restrict); which is not compatible with the