In the myconfig / perl -V output, like the following example:
Summary of my perl5 (5.0 patchlevel 4 subversion 1) configuration:
Platform:
osname=solaris, osvers=2.5, archname=sun4-solaris
uname='sunos lion 5.5 generic_103093-03 sun4m sparc sunw,sparcstation-10 '
hint=recommended, useposix=true, d_sigaction=define
bincompat3=y useperlio= d_sfio=
Compiler:
cc='gcc', optimize='-O6', gccversion=2.7.2.2
cppflags='-I/usr/local/include -I/opt/gnu/include'
ccflags ='-I/usr/local/include -I/opt/gnu/include'
stdchar='unsigned char', d_stdstdio=define, usevfork=false
voidflags=15, castflags=0, d_casti32=define, d_castneg=define
intsize=4, alignbytes=8, usemymalloc=y, randbits=15
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib -L/opt/gnu/lib'
libpth=/usr/local/lib /opt/gnu/lib /lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldb -ldl -lm -lc -lcrypt
libc=/lib/libc.so, so=so
useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=, ccdlflags=' '
cccdlflags='-fpic', lddlflags='-G -L/usr/local/lib -L/opt/gnu/lib'
I'd like to change $randbits, in the Compiler section, for $prototype.
Why remove randbits: randbits was added before we had such good and
informative tests in the test suite. The tests now pinpoint the problem
and explain the solution, including recommending the right value for randbits.
Why add prototype: In the medium term there may be advantages to moving
towards using ANSI C prototypes. At the moment there's no way of making
an impact assessment. This would be a first step. Especially when combined
with automated perlbug and perlbug -ok mail handling and archiving.
While I'm on the subject, libpth and libs values should be in quotes.
Any objections?
(Please don't turn this into a "my compiler doesn't support prototypes" rant.)
p5p-msgid:
199709290857.JAA07706@toad.ig.co.uk