🚀 go-pugleaf

Alan Curry wrote:
> In article <7rshd7Fa3vU1@mid.individual.net>,
> frank  <frank@example.invalid> wrote:
>>> dan@dan-desktop:~/source$ gcc -std=c99 -Wall -Wextra rd2.c -o out; ./out
>>> rd2.c: In function �process_directory�:
>>> rd2.c:40: warning: implicit declaration of function �readdir_r�
>>> rd2.c:48: warning: implicit declaration of function �lstat�
>>> rd2.c:66: warning: implicit declaration of function �readlink�
>>> dan@dan-desktop:~/source$ 
> 
> Every one of those functions has a "Feature Test Macro Requirements for
> glibc" note in the SYNOPSIS section of its man page. (If not, get some newer
> man pages.) Read those. Read the feature_test_macros(7) man page. Then add
> the necessary -D options to activate the set of features you want. WIth
> -std=c99 and no other feature-enabling macros defined, you get only the
> functions that are actually part of C99.
> 
> The quick way to enable just about everything is -D_GNU_SOURCE
> 

Bravo, Alan, you're always a clutch hitter.  I decided that I would use 
that in place of specifying a c standard, because I'm intentionally 
going to do things aren't defined by standard C as opposed to posix.

Given this intention, would you say this is an appropriate compile 
command line:

dan@dan-desktop:~/source$ gcc -D_GNU_SOURCE -Wall -Wextra rd3.c -o out

?  I'm not sure where I picked up -Wall and -Wextra.  Are they both 
still useful?

-- 
frank