Change 28595 by [EMAIL PROTECTED] on 2006/07/17 21:11:52
Remove the C89 checking with gcc
(but leave a note in perlhack)
Affected files ...
... //depot/perl/cflags.SH#32 edit
... //depot/perl/pod/perlhack.pod#115 edit
Differences ...
==== //depot/perl/cflags.SH#32 (xtext) ====
Index: perl/cflags.SH
--- perl/cflags.SH#31~28592~ 2006-07-16 23:51:54.000000000 -0700
+++ perl/cflags.SH 2006-07-17 14:11:52.000000000 -0700
@@ -91,21 +91,6 @@
stdflags=''
-# Be strict C89 for gcc (but not for g++).
-case "$gccversion" in
-'') ;;
-Intel*) ;; # Nice try, Intel C++.
-12]*) ;; # Go easy on the older versions of gcc.
-*) case "$cc" in
- *g++*) ;;
- *) case "$osname" in
- cygwin) ;; # Fails at least up to and including 1.5.20
- *) stdflags="$stdflags -std=c89" ;;
- esac
- esac
- ;;
-esac
-
echo "Extracting cflags (with variable substitutions)"
: This section of the file will have variable substitutions done on it.
: Move anything that needs config subs from !NO!SUBS! section to !GROK!THIS!.
==== //depot/perl/pod/perlhack.pod#115 (text) ====
Index: perl/pod/perlhack.pod
--- perl/pod/perlhack.pod#114~28588~ 2006-07-16 12:06:01.000000000 -0700
+++ perl/pod/perlhack.pod 2006-07-17 14:11:52.000000000 -0700
@@ -2462,9 +2462,9 @@
platforms as possible -- we will, anyway, and it's nice to save
oneself from public embarrassment.
-If using gcc, starting from Perl 5.9.4 Perl core C files will be
-compiled with the C<-std=c89> option which will hopefully catch
-most of these unportabilities.
+If using gcc, you can add the C<-std=c89> option which will hopefully
+catch most of these unportabilities. (However it might also catch
+incompatibilities in your system's header files.)
Use the Configure C<-Dgccansipedantic> flag to enable the gcc
C<-ansi -pedantic> flags which enforce stricter ANSI rules.
End of Patch.
