a2p
accept
access
acct
addftinfo
addr2line
adjtime
afmtodit
after
aio_cancel
aio_error
aio_read
aio_return
aio_suspend
aio_waitcomplete
aio_write
alias
aliases
alloc
anvil
append
apply
apropos
ar
array
as
asa
asn1parse
at
atq
atrm
attemptckalloc
attemptckrealloc
authlib
authtest
autopoint
awk
b64decode
b64encode
basename
batch
bc
bdes
bell
bg
bgerror
biff
big5
binary
bind
bindkey
bindtags
bindtextdomain
bio
bitmap
blowfish
bn
bootparams
bootptab
bounce
brandelf
break
breaksw
brk
bsdiff
bsdtar
bsnmpd
bspatch
bthost
btsockstat
buffer
builtin
builtins
bunzip2
button
byacc
bzcat
bzegrep
bzfgrep
bzgrep
bzip2
c2ph
c89
c99
ca
cal
calendar
canvas
cap_mkdb
case
cat
catch
catman
cc
cd
cdcontrol
chdir
checkbutton
checknr
chflags
chfn
chgrp
chio
chkey
chmod
chown
chpass
chroot
chsh
ci
ciphers
ckalloc
ckdist
ckfree
ckrealloc
cksum
cleanup
clear
clipboard
clock
clock_getres
clock_gettime
clock_settime
close
cmp
co
col
colcrt
colldef
colors
colrm
column
comm
command
compile_et
complete
compress
concat
config
connect
console
continue
core
courierlogger
couriertcpd
cp
cpan
cpio
cpp
creat
crl
crontab
crunchgen
crunchide
crypt
crypto
csh
csplit
ctags
ctm
ctm_dequeue
ctm_rmail
ctm_smail
cu
cursor
cursors
cut
cvs
date
dbiprof
dbiproxy
dc
dcgettext
dcngettext
dd
dde
default
defer
deliverquota
des
destroy
devfs
df
dgettext
dgst
dh
dhparam
dialog
diff
diff3
dig
dir
dirent
dirname
dirs
discard
disktab
dngettext
do
domainname
done
dprofpp
dsa
dsaparam
dtmfdecode
du
dup
dup2
eaccess
ec
ecdsa
echo
echotc
ecparam
ed
edit
editrc
ee
egrep
elf
elfdump
elif
else
enc
enc2xs
encoding
end
endif
endsw
engine
enigma
entry
env
envsubst
eof
eqn
err
errno
error
errstr
esac
ethers
euc
eui64
eval
event
evp
ex
exec
execve
exit
expand
export
exports
expr
extattr
extattr_delete_fd
extattr_delete_file
extattr_get_fd
extattr_get_file
extattr_set_fd
extattr_set_file
f77
false
famm
famx
fblocked
fbtab
fc
fchdir
fchflags
fchmod
fchown
fcntl
fconfigure
fcopy
fdescfs
fdformat
fdread
fdwrite
fetch
fg
fgrep
fhopen
fhstat
fhstatfs
fi
file
file2c
fileevent
filename
filetest
find
find2perl
finger
flex
flock
flush
fmt
focus
fold
font
fontedit
for
foreach
fork
format
forward
fpathconf
frame
from
fs
fstab
fstat
fstatfs
fsync
ftp
ftpchroot
ftpusers
ftruncate
futimes
g711conv
gb2312
gb18030
gbk
gcc
gcore
gcov
gdb
gencat
gendsa
genrsa
gensnmptree
getconf
getdents
getdirentries
getdtablesize
getegid
geteuid
getfacl
getfh
getfsstat
getgid
getgroups
getitimer
getlogin
getopt
getopts
getpeername
getpgid
getpgrp
getpid
getppid
getpriority
getresgid
getresuid
getrlimit
getrusage
gets
getsid
getsockname
getsockopt
gettext
gettextize
gettimeofday
gettytab
getuid
glob
global
gmake
goto
gperf
gprof
grab
grep
grid
grn
grodvi
groff
groff_font
groff_out
groff_tmac
grog
grolbp
grolj4
grops
grotty
group
groups
gunzip
gzcat
gzexe
gzip
h2ph
h2xs
hash
hashstat
hd
head
help2man
hesinfo
hexdump
history
host
hostname
hosts
hosts_access
hosts_options
hpftodit
http
hup
i386_get_ioperm
i386_get_ldt
i386_set_ioperm
i386_set_ldt
i386_vm86
iconv
id
ident
idprio
if
ifnames253
ifnames259
image
imapd
incr
indent
indxbib
info
infokey
inode
install
instmodsh
interp
intro
introduction
ioctl
ipcrm
ipcs
ipf
ipftest
ipnat
ippool
ipresend
issetugid
jail
jail_attach
jobid
jobs
join
jot
kbdcontrol
kbdmap
kcon
kdestroy
kdump
kenv
kevent
keycap
keylogin
keylogout
keymap
keysyms
kgdb
kill
killall
killpg
kinit
kldfind
kldfirstmod
kldload
kldnext
kldstat
kldsym
kldunload
klist
kpasswd
kqueue
kse
kse_create
kse_exit
kse_release
kse_switchin
kse_thr_interrupt
kse_wakeup
ktrace
label
labelframe
lam
lappend
last
lastcomm
lastlog
lchflags
lchmod
lchown
ld
ldap
ldapadd
ldapcompare
ldapdelete
ldapmodify
ldapmodrdn
ldappasswd
ldapsearch
ldapwhoami
ldd
leave
less
lesskey
lex
lgetfh
lhash
libnetcfg
library
limit
limits
lindex
link
linprocfs
linsert
lint
lio_listio
list
listbox
listen
lj4_font
lkbib
llength
lmtp
ln
load
loadfont
local
locale
locate
lock
lockf
log
logger
login
logins
logname
logout
look
lookbib
lorder
lower
lp
lpq
lpr
lprm
lptest
lrange
lreplace
ls
lsearch
lseek
lset
lsort
lstat
lsvfs
lutimes
lynx
m4
madvise
magic
mail
maildiracl
maildirkw
maildirmake
mailq
mailx
make
makeinfo
makewhatis
man
manpath
master
mc
mcedit
mcview
md2
md4
md5
mdc2
memory
menu
menubar
menubutton
merge
mesg
message
mincore
minherit
minigzip
mkdep
mkdir
mkfifo
mkimapdcert
mklocale
mknod
mkpop3dcert
mkstr
mktemp
mlock
mlockall
mmap
mmroff
modfind
modfnext
modnext
modstat
moduli
more
motd
mount
mprotect
mptable
msdos
msdosfs
msgattrib
msgcat
msgcmp
msgcomm
msgconv
msgen
msgexec
msgfilter
msgfmt
msggrep
msginit
msgmerge
msgs
msgunfmt
msguniq
mskanji
msql2mysql
msync
mt
munlock
munlockall
munmap
mv
myisamchk
myisamlog
myisampack
mysql
mysqlaccess
mysqladmin
mysqlbinlog
mysqlcheck
mysqld
mysqldump
mysqld_multi
mysqld_safe
mysqlhotcopy
mysqlimport
mysqlshow
mysql_config
mysql_fix_privilege_tables
mysql_zap
namespace
nanosleep
nawk
nc
ncal
ncplist
ncplogin
ncplogout
neqn
netconfig
netgroup
netid
netstat
networks
newaliases
newgrp
nex
nfsstat
nfssvc
ngettext
nice
nl
nm
nmount
nohup
nologin
notify
nroff
nseq
nslookup
ntp_adjtime
ntp_gettime
nvi
nview
objcopy
objdump
objformat
ocsp
od
onintr
open
openssl
opieaccess
opieinfo
opiekey
opiekeys
opiepasswd
option
options
oqmgr
pack
package
packagens
pagesize
palette
pam_auth
panedwindow
parray
passwd
paste
patch
pathchk
pathconf
pawd
pax
pbm
pcre
pcreapi
pcrebuild
pcrecallout
pcrecompat
pcrecpp
pcregrep
pcrematching
pcrepartial
pcrepattern
pcreperform
pcreposix
pcreprecompile
pcresample
pcretest
perl
perl56delta
perl58delta
perl561delta
perl570delta
perl571delta
perl572delta
perl573delta
perl581delta
perl582delta
perl583delta
perl584delta
perl585delta
perl586delta
perl587delta
perl588delta
perl5004delta
perl5005delta
perlaix
perlamiga
perlapi
perlapio
perlapollo
perlartistic
perlbeos
perlbook
perlboot
perlbot
perlbs2000
perlbug
perlcall
perlcc
perlce
perlcheat
perlclib
perlcn
perlcompile
perlcygwin
perldata
perldbmfilter
perldebguts
perldebtut
perldebug
perldelta
perldgux
perldiag
perldoc
perldos
perldsc
perlebcdic
perlembed
perlepoc
perlfaq
perlfaq1
perlfaq2
perlfaq3
perlfaq4
perlfaq5
perlfaq6
perlfaq7
perlfaq8
perlfaq9
perlfilter
perlfork
perlform
perlfreebsd
perlfunc
perlglossary
perlgpl
perlguts
perlhack
perlhist
perlhpux
perlhurd
perlintern
perlintro
perliol
perlipc
perlirix
perlivp
perljp
perlko
perllexwarn
perllinux
perllocale
perllol
perlmachten
perlmacos
perlmacosx
perlmint
perlmod
perlmodinstall
perlmodlib
perlmodstyle
perlmpeix
perlnetware
perlnewmod
perlnumber
perlobj
perlop
perlopenbsd
perlopentut
perlos2
perlos390
perlos400
perlothrtut
perlpacktut
perlplan9
perlpod
perlpodspec
perlport
perlqnx
perlre
perlref
perlreftut
perlrequick
perlreref
perlretut
perlrun
perlsec
perlsolaris
perlstyle
perlsub
perlsyn
perlthrtut
perltie
perltoc
perltodo
perltooc
perltoot
perltrap
perltru64
perltw
perlunicode
perluniintro
perlutil
perluts
perlvar
perlvmesa
perlvms
perlvos
perlwin32
perlxs
perlxstut
perror
pfbtops
pftp
pgrep
phones
photo
pic
pickup
piconv
pid
pipe
pkcs7
pkcs8
pkcs12
pkg_add
pkg_check
pkg_create
pkg_delete
pkg_info
pkg_sign
pkg_version
pkill
pl2pm
place
pod2html
pod2latex
pod2man
pod2text
pod2usage
podchecker
podselect
poll
popd
popup
posix_madvise
postalias
postcat
postconf
postdrop
postfix
postkick
postlock
postlog
postmap
postqueue
postsuper
pr
pread
preadv
printcap
printenv
printf
proc
procfs
profil
protocols
prove
proxymap
ps
psed
psroff
pstruct
ptrace
publickey
pushd
puts
pwd
pwrite
pwritev
qmgr
qmqpd
quota
quotactl
radiobutton
raise
rand
ranlib
rcp
rcs
rcsclean
rcsdiff
rcsfile
rcsfreeze
rcsintro
rcsmerge
read
readelf
readlink
readonly
readv
realpath
reboot
recv
recvfrom
recvmsg
red
ree
refer
regexp
registry
regsub
rehash
remote
rename
repeat
replace
req
reset
resolver
resource
return
rev
revoke
rfcomm_sppd
rfork
rhosts
ripemd
ripemd160
rlog
rlogin
rm
rmd160
rmdir
rpc
rpcgen
rs
rsa
rsautl
rsh
rtld
rtprio
rup
ruptime
rusers
rwall
rwho
s2p
safe
sasl
sasldblistusers2
saslpasswd2
sbrk
scache
scale
scan
sched
sched_getparam
sched_getscheduler
sched_get_priority_max
sched_get_priority_min
sched_rr_get_interval
sched_setparam
sched_setscheduler
sched_yield
scon
scp
script
scrollbar
sdiff
sed
seek
select
selection
semctl
semget
semop
send
sendbug
sendfile
sendmail
sendmsg
sendto
services
sess_id
set
setegid
setenv
seteuid
setfacl
setgid
setgroups
setitimer
setlogin
setpgid
setpgrp
setpriority
setregid
setresgid
setresuid
setreuid
setrlimit
setsid
setsockopt
settc
settimeofday
setty
setuid
setvar
sftp
sh
sha
sha1
sha256
shar
shells
shift
shmat
shmctl
shmdt
shmget
showq
shutdown
sigaction
sigaltstack
sigblock
sigmask
sigpause
sigpending
sigprocmask
sigreturn
sigsetmask
sigstack
sigsuspend
sigvec
sigwait
size
slapadd
slapcat
slapd
slapdn
slapindex
slappasswd
slaptest
sleep
slogin
slurpd
smbutil
smime
smtp
smtpd
socket
socketpair
sockstat
soelim
sort
source
spawn
speed
spinbox
spkac
splain
split
squid
squid_ldap_auth
squid_ldap_group
squid_unix_group
sscop
ssh
sshd_config
ssh_config
stab
startslip
stat
statfs
stop
string
strings
strip
stty
su
subst
sum
suspend
swapoff
swapon
switch
symlink
sync
sysarch
syscall
sysconftool
sysconftoolcheck
systat
s_client
s_server
s_time
tabs
tail
talk
tar
tbl
tclsh
tcltest
tclvars
tcopy
tcpdump
tcpslice
tcsh
tee
tell
telltc
telnet
term
termcap
terminfo
test
texindex
texinfo
text
textdomain
tfmtodit
tftp
then
threads
time
tip
tk
tkerror
tkvars
tkwait
tlsmgr
tmac
top
toplevel
touch
tput
tr
trace
trafshow
trap
troff
true
truncate
truss
tset
tsort
tty
ttys
type
tzfile
ui
ul
ulimit
umask
unalias
uname
uncomplete
uncompress
undelete
unexpand
unhash
unifdef
unifdefall
uniq
units
unknown
unlimit
unlink
unmount
unset
unsetenv
until
unvis
update
uplevel
uptime
upvar
usbhidaction
usbhidctl
users
utf8
utimes
utmp
utrace
uudecode
uuencode
uuidgen
vacation
variable
verify
version
vfork
vgrind
vgrindefs
vi
vidcontrol
vidfont
view
virtual
vis
vt220keys
vwait
w
wait
wait3
wait4
waitpid
wall
wc
wget
what
whatis
where
whereis
which
while
who
whoami
whois
window
winfo
wish
wm
write
writev
wtmp
x509
xargs
xgettext
xmlwf
xstr
xsubpp
yacc
yes
ypcat
ypchfn
ypchpass
ypchsh
ypmatch
yppasswd
ypwhich
yyfix
zcat
zcmp
zdiff
zegrep
zfgrep
zforce
zgrep
zmore
znew
_exit
__syscall
 
FreeBSD/Linux/UNIX General Commands Manual
Hypertext Man Pages
perlfaq1
 
PERLFAQ1(1)	       Perl Programmers Reference Guide 	   PERLFAQ1(1)



NAME
       perlfaq1 - General Questions About Perl ($Revision: 1.19 $, $Date:
       2005/12/31 00:54:37 $)

DESCRIPTION
       This section of the FAQ answers very general, high-level questions
       about Perl.

       What is Perl?

       Perl is a high-level programming language with an eclectic heritage
       written by Larry Wall and a cast of thousands.  It derives from the
       ubiquitous C programming language and to a lesser extent from sed, awk,
       the Unix shell, and at least a dozen other tools and languages.	Perl's
       process, file, and text manipulation facilities make it particularly
       well-suited for tasks involving quick prototyping, system utilities,
       software tools, system management tasks, database access, graphical
       programming, networking, and world wide web programming.  These
       strengths make it especially popular with system administrators and CGI
       script authors, but mathematicians, geneticists, journalists, and even
       managers also use Perl.	Maybe you should, too.

       Who supports Perl?  Who develops it?  Why is it free?

       The original culture of the pre-populist Internet and the deeply-held
       beliefs of Perl's author, Larry Wall, gave rise to the free and open
       distribution policy of perl.  Perl is supported by its users.  The
       core, the standard Perl library, the optional modules, and the documen-
       tation you're reading now were all written by volunteers.  See the per-
       sonal note at the end of the README file in the perl source distribu-
       tion for more details.  See perlhist (new as of 5.005) for Perl's mile-
       stone releases.

       In particular, the core development team (known as the Perl Porters)
       are a rag-tag band of highly altruistic individuals committed to pro-
       ducing better software for free than you could hope to purchase for
       money.  You may snoop on pending developments via the archives at
       http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/ and http://ar-
       chive.develooper.com/perl5-porters@perl.org/ or the news gateway
       nntp://nntp.perl.org/perl.perl5.porters or its web interface at
       http://nntp.perl.org/group/perl.perl5.porters , or read the faq at
       http://simon-cozens.org/writings/p5p-faq , or you can subscribe to the
       mailing list by sending perl5-porters-request@perl.org a subscription
       request (an empty message with no subject is fine).

       While the GNU project includes Perl in its distributions, there's no
       such thing as "GNU Perl".  Perl is not produced nor maintained by the
       Free Software Foundation.  Perl's licensing terms are also more open
       than GNU software's tend to be.

       You can get commercial support of Perl if you wish, although for most
       users the informal support will more than suffice.  See the answer to
       "Where can I buy a commercial version of perl?" for more information.

       Which version of Perl should I use?

       (contributed by brian d foy)

       There is often a matter of opinion and taste, and there isn't any one
       answer that fits anyone.  In general, you want to use either the cur-
       rent stable release, or the stable release immediately prior to that
       one.  Currently, those are perl5.8.x and perl5.6.x, respectively.

       Beyond that, you have to consider several things and decide which is
       best for you.

       o   If things aren't broken, upgrading perl may break them (or at least
	   issue new warnings).

       o   The latest versions of perl have more bug fixes.

       o   The Perl community is geared toward supporting the most recent
	   releases, so you'll have an easier time finding help for those.

       o   Versions prior to perl5.004 had serious security problems with
	   buffer overflows, and in some cases have CERT advisories (for
	   instance, http://www.cert.org/advisories/CA-1997-17.html ).

       o   The latest versions are probably the least deployed and widely
	   tested, so you may want to wait a few months after their release
	   and see what problems others have if you are risk averse.

       o   The immediate, previous releases (i.e. perl5.6.x ) are usually
	   maintained for a while, although not at the same level as the cur-
	   rent releases.

       o   No one is actively supporting perl4.x.  Five years ago it was a
	   dead camel carcass (according to this document).  Now it's barely a
	   skeleton as its whitewashed bones have fractured or eroded.

       o   There is no perl6.x for the next couple of years.  Stay tuned, but
	   don't worry that you'll have to change major versions of Perl soon
	   (i.e. before 2006).

       o   There are really two tracks of perl development: a maintenance ver-
	   sion and an experimental version.  The maintenance versions are
	   stable, and have an even number as the minor release (i.e.
	   perl5.8.x, where 8 is the minor release).  The experimental ver-
	   sions may include features that don't make it into the stable ver-
	   sions, and have an odd number as the minor release (i.e. perl5.9.x,
	   where 9 is the minor release).

       What are perl4, perl5, or perl6?

       (contributed by brian d foy)

       In short, perl4 is the past, perl5 is the present, and perl6 is the
       future.

       The number after perl (i.e. the 5 after perl5) is the major release of
       the perl interpreter as well as the version of the language.  Each
       major version has significant differences that earlier versions cannot
       support.

       The current major release of Perl is perl5, and was released in 1994.
       It can run scripts from the previous major release, perl4 (March 1991),
       but has significant differences. It introduced the concept of refer-
       ences, complex data structures, and modules.  The perl5 interpreter was
       a complete re-write of the previous perl sources.

       Perl6 is the next major version of Perl, but it's still in development
       in both its syntax and design.  The work started in 2002 and is still
       ongoing.  Many of the most interesting features have shown up in the
       latest versions of perl5, and some perl5 modules allow you to use some
       perl6 syntax in your programs.  You can learn more about perl6 at
       http://dev.perl.org/perl6/ .

       See perlhist for a history of Perl revisions.

       What is Ponie?

       At The O'Reilly Open Source Software Convention in 2003, Artur Bergman,
       Fotango, and The Perl Foundation announced a project to run perl5 on
       the Parrot virtual machine named Ponie. Ponie stands for Perl On New
       Internal Engine.  The Perl 5.10 language implementation will be used
       for Ponie, and there will be no language level differences between
       perl5 and ponie.  Ponie is not a complete rewrite of perl5.

       For more details, see http://www.poniecode.org/

       What is perl6?

       At The Second O'Reilly Open Source Software Convention, Larry Wall
       announced Perl6 development would begin in earnest. Perl6 was an oft
       used term for Chip Salzenberg's project to rewrite Perl in C++ named
       Topaz. However, Topaz provided valuable insights to the next version of
       Perl and its implementation, but was ultimately abandoned.

       If you want to learn more about Perl6, or have a desire to help in the
       crusade to make Perl a better place then peruse the Perl6 developers
       page at http://dev.perl.org/perl6/ and get involved.

       Perl6 is not scheduled for release yet, and Perl5 will still be sup-
       ported for quite awhile after its release. Do not wait for Perl6 to do
       whatever you need to do.

       "We're really serious about reinventing everything that needs reinvent-
       ing."  --Larry Wall

       How stable is Perl?

       Production releases, which incorporate bug fixes and new functionality,
       are widely tested before release.  Since the 5.000 release, we have
       averaged only about one production release per year.

       Larry and the Perl development team occasionally make changes to the
       internal core of the language, but all possible efforts are made toward
       backward compatibility.	While not quite all perl4 scripts run flaw-
       lessly under perl5, an update to perl should nearly never invalidate a
       program written for an earlier version of perl (barring accidental bug
       fixes and the rare new keyword).

       Is Perl difficult to learn?

       No, Perl is easy to start learning--and easy to keep learning.  It
       looks like most programming languages you're likely to have experience
       with, so if you've ever written a C program, an awk script, a shell
       script, or even a BASIC program, you're already partway there.

       Most tasks only require a small subset of the Perl language.  One of
       the guiding mottos for Perl development is "there's more than one way
       to do it" (TMTOWTDI, sometimes pronounced "tim toady").	Perl's learn-
       ing curve is therefore shallow (easy to learn) and long (there's a
       whole lot you can do if you really want).

       Finally, because Perl is frequently (but not always, and certainly not
       by definition) an interpreted language, you can write your programs and
       test them without an intermediate compilation step, allowing you to
       experiment and test/debug quickly and easily.  This ease of experimen-
       tation flattens the learning curve even more.

       Things that make Perl easier to learn: Unix experience, almost any kind
       of programming experience, an understanding of regular expressions, and
       the ability to understand other people's code.  If there's something
       you need to do, then it's probably already been done, and a working
       example is usually available for free.  Don't forget the new perl mod-
       ules, either.  They're discussed in Part 3 of this FAQ, along with
       CPAN, which is discussed in Part 2.

       How does Perl compare with other languages like Java, Python, REXX,
       Scheme, or Tcl?

       Favorably in some areas, unfavorably in others.	Precisely which areas
       are good and bad is often a personal choice, so asking this question on
       Usenet runs a strong risk of starting an unproductive Holy War.

       Probably the best thing to do is try to write equivalent code to do a
       set of tasks.  These languages have their own newsgroups in which you
       can learn about (but hopefully not argue about) them.

       Some comparison documents can be found at
       http://www.perl.com/doc/FMTEYEWTK/versus/ if you really can't stop
       yourself.

       Can I do [task] in Perl?

       Perl is flexible and extensible enough for you to use on virtually any
       task, from one-line file-processing tasks to large, elaborate systems.
       For many people, Perl serves as a great replacement for shell script-
       ing.  For others, it serves as a convenient, high-level replacement for
       most of what they'd program in low-level languages like C or C++.  It's
       ultimately up to you (and possibly your management) which tasks you'll
       use Perl for and which you won't.

       If you have a library that provides an API, you can make any component
       of it available as just another Perl function or variable using a Perl
       extension written in C or C++ and dynamically linked into your main
       perl interpreter.  You can also go the other direction, and write your
       main program in C or C++, and then link in some Perl code on the fly,
       to create a powerful application.  See perlembed.

       That said, there will always be small, focused, special-purpose lan-
       guages dedicated to a specific problem domain that are simply more con-
       venient for certain kinds of problems.  Perl tries to be all things to
       all people, but nothing special to anyone.  Examples of specialized
       languages that come to mind include prolog and matlab.

       When shouldn't I program in Perl?

       When your manager forbids it--but do consider replacing them :-).

       Actually, one good reason is when you already have an existing applica-
       tion written in another language that's all done (and done well), or
       you have an application language specifically designed for a certain
       task (e.g. prolog, make).

       For various reasons, Perl is probably not well-suited for real-time
       embedded systems, low-level operating systems development work like
       device drivers or context-switching code, complex multi-threaded
       shared-memory applications, or extremely large applications.  You'll
       notice that perl is not itself written in Perl.

       The new, native-code compiler for Perl may eventually reduce the limi-
       tations given in the previous statement to some degree, but understand
       that Perl remains fundamentally a dynamically typed language, not a
       statically typed one.  You certainly won't be chastised if you don't
       trust nuclear-plant or brain-surgery monitoring code to it.  And Larry
       will sleep easier, too--Wall Street programs not withstanding. :-)

       What's the difference between "perl" and "Perl"?

       One bit.  Oh, you weren't talking ASCII? :-) Larry now uses "Perl" to
       signify the language proper and "perl" the implementation of it, i.e.
       the current interpreter.  Hence Tom's quip that "Nothing but perl can
       parse Perl."  You may or may not choose to follow this usage.  For
       example, parallelism means "awk and perl" and "Python and Perl" look
       OK, while "awk and Perl" and "Python and perl" do not.  But never write
       "PERL", because perl is not an acronym, apocryphal folklore and post-
       facto expansions notwithstanding.

       Is it a Perl program or a Perl script?

       Larry doesn't really care.  He says (half in jest) that "a script is
       what you give the actors.  A program is what you give the audience."

       Originally, a script was a canned sequence of normally interactive com-
       mands--that is, a chat script.  Something like a UUCP or PPP chat
       script or an expect script fits the bill nicely, as do configuration
       scripts run by a program at its start up, such .cshrc or .ircrc, for
       example.  Chat scripts were just drivers for existing programs, not
       stand-alone programs in their own right.

       A computer scientist will correctly explain that all programs are
       interpreted and that the only question is at what level.  But if you
       ask this question of someone who isn't a computer scientist, they might
       tell you that a program has been compiled to physical machine code once
       and can then be run multiple times, whereas a script must be translated
       by a program each time it's used.

       Perl programs are (usually) neither strictly compiled nor strictly
       interpreted.  They can be compiled to a byte-code form (something of a
       Perl virtual machine) or to completely different languages, like C or
       assembly language.  You can't tell just by looking at it whether the
       source is destined for a pure interpreter, a parse-tree interpreter, a
       byte-code interpreter, or a native-code compiler, so it's hard to give
       a definitive answer here.

       Now that "script" and "scripting" are terms that have been seized by
       unscrupulous or unknowing marketeers for their own nefarious purposes,
       they have begun to take on strange and often pejorative meanings, like
       "non serious" or "not real programming".  Consequently, some Perl pro-
       grammers prefer to avoid them altogether.

       What is a JAPH?

       These are the "just another perl hacker" signatures that some people
       sign their postings with.  Randal Schwartz made these famous.  About
       100 of the earlier ones are available from
       http://www.cpan.org/misc/japh .

       Where can I get a list of Larry Wall witticisms?

       Over a hundred quips by Larry, from postings of his or source code, can
       be found at http://www.cpan.org/misc/lwall-quotes.txt.gz .

       How can I convince my sysadmin/supervisor/employees to use version
       5/5.6.1/Perl instead of some other language?

       If your manager or employees are wary of unsupported software, or soft-
       ware which doesn't officially ship with your operating system, you
       might try to appeal to their self-interest.  If programmers can be more
       productive using and utilizing Perl constructs, functionality, simplic-
       ity, and power, then the typical manager/supervisor/employee may be
       persuaded.  Regarding using Perl in general, it's also sometimes help-
       ful to point out that delivery times may be reduced using Perl compared
       to other languages.

       If you have a project which has a bottleneck, especially in terms of
       translation or testing, Perl almost certainly will provide a viable,
       quick solution.	In conjunction with any persuasion effort, you should
       not fail to point out that Perl is used, quite extensively, and with
       extremely reliable and valuable results, at many large computer soft-
       ware and hardware companies throughout the world.  In fact, many Unix
       vendors now ship Perl by default.  Support is usually just a news-post-
       ing away, if you can't find the answer in the comprehensive documenta-
       tion, including this FAQ.

       See http://www.perl.org/advocacy/ for more information.

       If you face reluctance to upgrading from an older version of perl, then
       point out that version 4 is utterly unmaintained and unsupported by the
       Perl Development Team.  Another big sell for Perl5 is the large number
       of modules and extensions which greatly reduce development time for any
       given task.  Also mention that the difference between version 4 and
       version 5 of Perl is like the difference between awk and C++.  (Well,
       OK, maybe it's not quite that distinct, but you get the idea.)  If you
       want support and a reasonable guarantee that what you're developing
       will continue to work in the future, then you have to run the supported
       version.  As of December 2003 that means running either 5.8.2 (released
       in November 2003), or one of the older releases like 5.6.2 (also
       released in November 2003; a maintenance release to let perl 5.6 com-
       pile on newer systems as 5.6.1 was released in April 2001) or 5.005_03
       (released in March 1999), although 5.004_05 isn't that bad if you abso-
       lutely need such an old version (released in April 1999) for stability
       reasons.  Anything older than 5.004_05 shouldn't be used.

       Of particular note is the massive bug hunt for buffer overflow problems
       that went into the 5.004 release.  All releases prior to that, includ-
       ing perl4, are considered insecure and should be upgraded as soon as
       possible.

       In August 2000 in all Linux distributions a new security problem was
       found in the optional 'suidperl' (not built or installed by default) in
       all the Perl branches 5.6, 5.005, and 5.004, see
       http://www.cpan.org/src/5.0/sperl-2000-08-05/ Perl maintenance releases
       5.6.1 and 5.8.0 have this security hole closed.	Most, if not all,
       Linux distribution have patches for this vulnerability available, see
       http://www.linuxsecurity.com/advisories/ , but the most recommendable
       way is to upgrade to at least Perl 5.6.1.

AUTHOR AND COPYRIGHT
       Copyright (c) 1997-2006 Tom Christiansen, Nathan Torkington, and other
       authors as noted. All rights reserved.

       This documentation is free; you can redistribute it and/or modify it
       under the same terms as Perl itself.

       Irrespective of its distribution, all code examples here are in the
       public domain.  You are permitted and encouraged to use this code and
       any derivatives thereof in your own programs for fun or for profit as
       you see fit.  A simple comment in the code giving credit to the FAQ
       would be courteous but is not required.



perl v5.8.8			  2006-01-07			   PERLFAQ1(1)
=18975
+293
(73)