[8904] in Perl-Users-Digest
Perl-Users Digest, Issue: 2521 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed May 6 20:07:32 1998
Date: Wed, 6 May 98 17:01:42 -0700
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 6 May 1998 Volume: 8 Number: 2521
Today's topics:
How old is Perl? <kviggers@gulf.uvic.ca>
Re: How old is Perl? (Stuart McDow)
Re: How old is Perl? <tkil@scrye.com>
Re: How old is Perl? <tchrist@mox.perl.com>
Re: How to compare to files <ebohlman@netcom.com>
Re: IS THIS POSSIBE IN PERL! (Martien Verbruggen)
Re: Localtime--dumb question probably (Martien Verbruggen)
Re: Looking for Perl parser for 'C' language input file (Damian Conway)
Re: Open to suggestions <ebohlman@netcom.com>
Re: passing .htaccess login info <bwsd@bwsd.com>
Re: Problem installing Perl 5.004_04 on Solaris 2.5.1 (Martien Verbruggen)
Re: problem with cat <danboo@negia.net>
Re: problem with cat <dformosa@st.nepean.uws.edu.au>
Re: Problem with prune in File::Find <jdf@pobox.com>
Re: References <dformosa@st.nepean.uws.edu.au>
Re: Script Needed: Referral/Affiliate/Commission reward (Martien Verbruggen)
Re: Splain a regex to me (Martien Verbruggen)
Re: Win32: Can't locate auto/Text/ParseWords/quotewords <bryan@eai.com>
Digest Administrivia (Last modified: 8 Mar 97) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 06 May 1998 15:04:39 -0700
From: "K. Viggers" <kviggers@gulf.uvic.ca>
Subject: How old is Perl?
Message-Id: <3550DE76.B410C9BA@gulf.uvic.ca>
I was just hoping that someone could tell me when Perl began its
exsistence.
Thanks
Kevin
------------------------------
Date: 6 May 1998 22:52:48 GMT
From: smcdow@arlut.utexas.edu (Stuart McDow)
Subject: Re: How old is Perl?
Message-Id: <6iqpk0$s8p$1@ns1.arlut.utexas.edu>
"K. Viggers" <kviggers@gulf.uvic.ca> writes:
>
> I was just hoping that someone could tell me when Perl began its
> exsistence.
see http://www.perl.com/971220.html
--
Stuart McDow Applied Research Laboratories
smcdow@arlut.utexas.edu The University of Texas at Austin
"It is obvious that about 750,000 people ago, Austin was a wonderful City."
------------------------------
Date: 06 May 1998 17:03:50 -0600
From: Tkil <tkil@scrye.com>
Subject: Re: How old is Perl?
Message-Id: <ghg33j92h.fsf@scrye.com>
>>>>> "Kevin" == K Viggers <kviggers@gulf.uvic.ca> writes:
Kevin> I was just hoping that someone could tell me when Perl began
Kevin> its exsistence.
Perl turned 10 last year:
http://www.perl.com/971220.html
with December 18th, 1987 being pegged as the official birthday.
t.
--
Tkil * <URL: http://www.scrye.com/~tkil> * hopelessly hopeless romantic.
"So amplify this little one | She hears as much as she can see
She's a volume freak | And what she sees, she can't believe."
-- Catherine Wheel, _Happy Days_, "Judy Staring At The Sun"
------------------------------
Date: 6 May 1998 23:29:52 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: How old is Perl?
Message-Id: <6iqrpg$kk2$1@csnews.cs.colorado.edu>
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc, "K. Viggers" <kviggers@gulf.uvic.ca> writes:
: I was just hoping that someone could tell me when Perl began its
:existence.
NAME
perlhist - the Perl history records
DESCRIPTION
This document aims to record the Perl source code releases.
INTRODUCTION
Perl history in brief, by Larry Wall:
Perl 0 introduced Perl to my officemates.
Perl 1 introduced Perl to the world, and changed /\(...\|...\)/ to
/(...|...)/. \(Dan Faigin still hasn't forgiven me. :-\)
Perl 2 introduced Henry Spencer's regular expression package.
Perl 3 introduced the ability to handle binary data (embedded nulls).
Perl 4 introduced the first Camel book. Really. We mostly just
switched version numbers so the book could refer to 4.000.
Perl 5 introduced everything else, including the ability to
introduce everything else.
THE KEEPERS OF THE PUMPKIN
Larry Wall, Andy Dougherty, Tom Christiansen, Charles Bailey, Nick
Ing-Simmons, Chip Salzenberg, Tim Bunce, Malcolm Beattie.
PUMPKIN?
[from Porting/pumpkin.pod in the Perl source code distribution]
Chip Salzenberg gets credit for that, with a nod to his cow orker,
David Croy. We had passed around various names (baton, token,
hot potato) but none caught on. Then, Chip asked:
[begin quote]
Who has the patch pumpkin?
To explain: David Croy once told me once that at a previous job, there
was one tape drive and multiple systems that used it for backups. But
instead of some high-tech exclusion software, they used a low-tech
method to prevent multiple simultaneous backups: a stuffed pumpkin. No
one was allowed to make backups unless they had the "backup pumpkin".
[end quote]
The name has stuck. The holder of the pumpkin is sometimes called
the pumpking or the pumpkineer.
THE RECORDS
Pump- Release Date Notes
king (by no means
comprehensive,
see Changes*
for details)
===========================================================================
Larry 0 Classified. Don't ask.
Larry 1.000 1987-Dec-18
1.001..10 1988-Jan-30
1.011..14 1988-Feb-02
Larry 2.000 1988-Jun-05
2.001 1988-Jun-28
Larry 3.000 1989-Oct-18
3.001 1989-Oct-26
3.002..4 1989-Nov-11
3.005 1989-Nov-18
3.006..8 1989-Dec-22
3.009..13 1990-Mar-02
3.014 1990-Mar-13
3.015 1990-Mar-14
3.016..18 1990-Mar-28
3.019..27 1990-Aug-10 User subs.
3.028 1990-Aug-14
3.029..36 1990-Oct-17
3.037 1990-Oct-20
3.040 1990-Nov-10
3.041 1990-Nov-13
3.042..43 1990-Jan-91
3.044 1991-Jan-12
Larry 4.000 1991-Mar-21
4.001..3 1991-Apr-12
4.004..9 1991-Jun-07
4.010 1991-Jun-10
4.011..18 1991-Nov-05
4.019 1991-Nov-11 Stable.
4.020..33 1992-Jun-08
4.034 1992-Jun-11
4.035 1992-Jun-23
Larry 4.036 1993-Feb-05 Very stable.
5.000alpha1 1993-Jul-31
5.000alpha2 1993-Aug-16
5.000alpha3 1993-Oct-10
5.000alpha4 1993-???-??
5.000alpha5 1993-???-??
5.000alpha6 1993-Mar-18
5.003alpha7 1994-Mar-25
Andy 5.000alpha8 1994-Apr-04
Larry 5.000alpha9 1994-May-05 ext appears.
5.000alpha10 1994-???-??
5.000alpha11 1994-???-??
Andy 5.000a11a 1994-Jul-07 To fit 14.
5.000a11b 1994-Jul-14
5.000a11c 1994-Jul-19
5.000a11d 1994-Jul-22
Larry 5.000alpha12 1994-???-??
Andy 5.000a12a 1994-Aug-08
5.000a12b 1994-Aug-15
5.000a12c 1994-Aug-22
5.000a12d 1994-Aug-22
5.000a12e 1994-Aug-22
5.000a12f 1994-Aug-24
5.000a12g 1994-Aug-24
5.000a12h 1994-Aug-24
Larry 5.000beta1 1994-???-??
Andy 5.000b1a 1994-???-??
Larry 5.000beta2 1994-Sep-14 Core slushified.
Andy 5.000b2a 1994-Sep-14
5.000b2b 1994-Sep-17
5.000b2c 1994-Sep-17
Larry 5.000beta3 1994-???-??
Andy 5.000b3a 1994-Sep-18
5.000b3b 1994-Sep-22
5.000b3c 1994-Sep-23
5.000b3d 1994-Sep-27
5.000b3e 1994-Sep-28
5.000b3f 1994-Sep-30
5.000b3g 1994-Oct-04
Andy 5.000b3h 1994-Oct-07
Larry 5.000 1994-Oct-18
Andy 5.000a 1994-Dec-19
5.000b 1995-Jan-18
5.000c 1995-Jan-18
5.000d 1995-Jan-18
5.000e 1995-Jan-18
5.000f 1995-Jan-18
5.000g 1995-Jan-18
5.000h 1995-Jan-18
5.000i 1995-Jan-26
5.000j 1995-Feb-07
5.000k 1995-Feb-11
5.000l 1995-Feb-21
5.000m 1995-???-??
5.000n 1995-Mar-07
Larry 5.001 1995-Mar-13
Andy 5.001a 1995-Mar-15
5.001b 1995-Mar-31
5.001c 1995-Apr-07
5.001d 1995-Apr-14
5.001e 1995-Apr-18 Stable.
5.001f 1995-May-31
5.001g 1995-May-25
5.001h 1995-May-25
5.001i 1995-May-30
5.001j 1995-Jun-05
5.001k 1995-Jun-06
5.001l 1995-Jun-06 Stable.
5.001m 1995-Jul-02 Very stable.
5.001n 1995-Oct-31 Very unstable.
5.002beta1 1995-Nov-21
5.002b1a 1995-Nov-??
5.002b1b 1995-Dec-04
5.002b1c 1995-Dec-04
5.002b1d 1995-Dec-04
5.002b1e 1995-Dec-08
5.002b1f 1995-Dec-08
Tom 5.002b1g 1995-Dec-21 Doc release.
Andy 5.002b1h 1996-Jan-05
5.002b2 1996-Jan-14
Larry 5.002b3 1996-Feb-02
Andy 5.002gamma 1996-Feb-11
Larry 5.002delta 1996-Feb-27
Larry 5.002 1996-Feb-29
Charles 5.002_01 1996-Mar-25
5.003 1996-Jun-25 Security release.
5.003_01 1996-Jul-31
Nick 5.003_02 1996-Aug-10
Andy 5.003_03 1996-Aug-28
5.003_04 1996-Sep-02
5.003_05 1996-Sep-12
5.003_06 1996-Oct-07
5.003_07 1996-Oct-10
Chip 5.003_08 1996-Nov-19
5.003_09 1996-Nov-26
5.003_10 1996-Nov-29
5.003_11 1996-Dec-06
5.003_12 1996-Dec-19
5.003_13 1996-Dec-20
5.003_14 1996-Dec-23
5.003_15 1996-Dec-23
5.003_16 1996-Dec-24
5.003_17 1996-Dec-27
5.003_18 1996-Dec-31
5.003_19 1997-Jan-04
5.003_20 1997-Jan-07
5.003_21 1997-Jan-15
5.003_22 1997-Jan-16
5.003_23 1997-Jan-25
5.003_24 1997-Jan-29
5.003_25 1997-Feb-04
5.003_26 1997-Feb-10
5.003_27 1997-Feb-18
5.003_28 1997-Feb-21
5.003_90 1997-Feb-25 Ramping up to the 5.004 release.
5.003_91 1997-Mar-01
5.003_92 1997-Mar-06
5.003_93 1997-Mar-10
5.003_94 1997-Mar-22
5.003_95 1997-Mar-25
5.003_96 1997-Apr-01
5.003_97 1997-Apr-03 Fairly widely used.
5.003_97a 1997-Apr-05
5.003_97b 1997-Apr-08
5.003_97c 1997-Apr-10
5.003_97d 1997-Apr-13
5.003_97e 1997-Apr-15
5.003_97f 1997-Apr-17
5.003_97g 1997-Apr-18
5.003_97h 1997-Apr-24
5.003_97i 1997-Apr-25
5.003_97j 1997-Apr-28
5.003_98 1997-Apr-30
5.003_99 1997-May-01
5.003_99a 1997-May-09
p54rc1 1997-May-12 Release Candidates.
p54rc2 1997-May-14
Chip 5.004 1997-May-15 A major maintenance release.
Tim 5.004_01 1997-Jun-13 The 5.004 maintenance track.
5.004_02 1997-Aug-07
5.004_03 1997-Sep-05
5.004_04 1997-Oct-15
Malcolm 5.004_50 1997-Sep-09 The 5.005 development track.
5.004_51 1997-Oct-02
5.004_52 1997-Oct-15
5.004_53 1997-Oct-16
5.004_54 1997-Nov-14
5.004_55 1997-Nov-25
5.004_56 1997-Dec-18
5.004_57 1998-Feb-03
5.004_58 1998-Feb-06
5.004_59 1998-Feb-13
5.004_60 1998-Feb-20
5.004_61 1998-Feb-27
5.004_62 1998-Mar-06
5.004_63 1998-Mar-17
5.004_64 1998-Apr-03
SELECTED RELEASE SIZES
For example the notation "core: 212 29" in the release 1.000 means that it had
in the core 212 kilobytes, in 29 files. The "core".."doc" are explained below.
release core lib ext t doc
======================================================================
1.000 212 29 - - - - 38 51 62 3
1.014 219 29 - - - - 39 52 68 4
2.000 309 31 2 3 - - 55 57 92 4
2.001 312 31 2 3 - - 55 57 94 4
3.000 508 36 24 11 - - 79 73 156 5
3.044 645 37 61 20 - - 90 74 190 6
4.000 635 37 59 20 - - 91 75 198 4
4.019 680 37 85 29 - - 98 76 199 4
4.036 709 37 89 30 - - 98 76 208 5
5.000alpha2 785 50 114 32 - - 112 86 209 5
5.000a3 801 50 117 33 - - 121 87 209 5
5.000a9 1022 56 149 43 116 29 125 90 217 6
5.000a12h 978 49 140 49 205 46 152 97 228 9
5.000beta3h 1035 53 232 70 216 38 162 94 218 21
5.000 1038 53 250 76 216 38 154 92 536 62
5.001m 1071 54 388 82 240 38 159 95 544 29
5.002 1121 54 661 101 287 43 155 94 847 35
5.003 1129 54 680 102 291 43 166 100 853 35
5.003_07 1231 60 748 106 396 53 213 137 976 39
5.004 1351 60 1230 136 408 51 355 161 1587 55
5.004_01 1356 60 1258 138 410 51 358 161 1587 55
5.004_04 1375 60 1294 139 413 51 394 162 1629 55
5.004_51 1401 61 1260 140 413 53 358 162 1594 56
5.004_53 1422 62 1295 141 438 70 394 162 1637 56
5.004_56 1501 66 1301 140 447 74 408 165 1648 57
5.004_59 1555 72 1317 142 448 74 424 171 1678 58
5.004_62 1602 77 1327 144 629 92 428 173 1674 58
The "core"..."doc" mean the following files from the Perl source
code distribution. The glob notation ** means recursively, (.) means
regular files.
core *.[hcy]
lib lib/**/*.p[ml]
ext ext/**/*.{[hcyt],xs,pm}
t t/**/*(.)
doc {README*,INSTALL,*[_.]man{,.?},pod/**/*.pod}
Here are some statistics for the other subdirectories and one file
in the Perl source distribution for somewhat more selected releases.
======================================================================
Legend: kB #
1.014 2.001 3.044 4.000 4.019 4.036
atarist - - - - - - - - - - 113 31
Configure 31 1 37 1 62 1 73 1 83 1 86 1
eg - - 34 28 47 39 47 39 47 39 47 39
emacs - - - - - - 67 4 67 4 67 4
h2pl - - - - 12 12 12 12 12 12 12 12
hints - - - - - - - - 5 42 11 56
msdos - - - - 41 13 57 15 58 15 60 15
os2 - - - - 63 22 81 29 81 29 113 31
usub - - - - 21 16 25 7 43 8 43 8
x2p 103 17 104 17 137 17 147 18 152 19 154 19
======================================================================
5.000a2 5.000a12h 5.000b3h 5.000 5.001m 5.002 5.003
atarist 113 31 113 31 - - - - - - - - - -
bench - - 0 1 - - - - - - - - - -
Bugs 2 5 26 1 - - - - - - - - - -
dlperl 40 5 - - - - - - - - - - - -
do 127 71 - - - - - - - - - - - -
Configure - - 153 1 159 1 160 1 180 1 201 1 201 1
Doc - - 26 1 75 7 11 1 11 1 - - - -
eg 79 58 53 44 51 43 54 44 54 44 54 44 54 44
emacs 67 4 104 6 104 6 104 1 104 6 108 1 108 1
h2pl 12 12 12 12 12 12 12 12 12 12 12 12 12 12
hints 11 56 12 46 18 48 18 48 44 56 73 59 77 60
msdos 60 15 60 15 - - - - - - - - - -
os2 113 31 113 31 - - - - - - 84 17 56 10
U - - 62 8 112 42 - - - - - - - -
usub 43 8 - - - - - - - - - - - -
utils - - - - - - - - - - 87 7 88 7
vms - - 80 7 123 9 184 15 304 20 500 24 475 26
x2p 171 22 171 21 162 20 162 20 279 20 280 20 280 20
======================================================================
5.003_07 5.004 5.004_04 5.004_62
Configure 217 1 225 1 225 1 240 1
cygwin32 - - 23 5 23 5 23 5
djgpp - - - - - - 14 5
eg 54 44 81 62 81 62 81 62
emacs 143 1 194 1 204 1 212 2
h2pl 12 12 12 12 12 12 12 12
hints 90 62 129 69 132 71 144 72
os2 117 42 121 42 127 42 127 44
plan9 79 15 82 15 82 15 82 15
Porting 51 1 94 2 109 4 203 6
qnx - - 1 2 1 2 1 2
utils 97 7 112 8 118 8 124 8
vms 505 27 518 34 524 34 538 34
win32 - - 285 33 378 36 470 39
x2p 280 19 281 19 281 19 281 19
SELECTED PATCH SIZES
The "diff lines kb" means that for example the patch 5.003_08, to
be applied on top 5.003_07 (or whatever was before it) added lines
for 110 kilobytes, it removed lines for 19 kilobytes, and changed
lines for 424 kilobytes. Just the lines themselves are counted,
not their context. The "+ - !" become from the diff(1)s context diff
output format.
Pump- Release Date diff lines kB
king + - !
===========================================================================
Chip 5.003_08 1996-Nov-19 110 19 424
5.003_09 1996-Nov-26 38 9 248
5.003_10 1996-Nov-29 29 2 27
5.003_11 1996-Dec-06 73 12 165
5.003_12 1996-Dec-19 275 6 436
5.003_13 1996-Dec-20 95 1 56
5.003_14 1996-Dec-23 23 7 333
5.003_15 1996-Dec-23 0 0 1
5.003_16 1996-Dec-24 12 3 50
5.003_17 1996-Dec-27 19 1 14
5.003_18 1996-Dec-31 21 1 32
5.003_19 1997-Jan-04 80 3 85
5.003_20 1997-Jan-07 18 1 146
5.003_21 1997-Jan-15 38 10 221
5.003_22 1997-Jan-16 4 0 18
5.003_23 1997-Jan-25 71 15 119
5.003_24 1997-Jan-29 426 1 20
5.003_25 1997-Feb-04 21 8 169
5.003_26 1997-Feb-10 16 1 15
5.003_27 1997-Feb-18 32 10 38
5.003_28 1997-Feb-21 58 4 66
5.003_90 1997-Feb-25 22 2 34
5.003_91 1997-Mar-01 37 1 39
5.003_92 1997-Mar-06 16 3 69
5.003_93 1997-Mar-10 12 3 15
5.003_94 1997-Mar-22 407 7 200
5.003_95 1997-Mar-25 41 1 37
5.003_96 1997-Apr-01 283 5 261
5.003_97 1997-Apr-03 13 2 34
5.003_97a 1997-Apr-05 57 1 27
5.003_97b 1997-Apr-08 14 1 20
5.003_97c 1997-Apr-10 20 1 16
5.003_97d 1997-Apr-13 8 0 16
5.003_97e 1997-Apr-15 15 4 46
5.003_97f 1997-Apr-17 7 1 33
5.003_97g 1997-Apr-18 6 1 42
5.003_97h 1997-Apr-24 23 3 68
5.003_97i 1997-Apr-25 23 1 31
5.003_97j 1997-Apr-28 36 1 49
5.003_98 1997-Apr-30 171 12 539
5.003_99 1997-May-01 6 0 7
5.003_99a 1997-May-09 36 2 61
p54rc1 1997-May-12 8 1 11
p54rc2 1997-May-14 6 0 40
5.004 1997-May-15 4 0 4
Tim 5.004_01 1997-Jun-13 222 14 57
5.004_02 1997-Aug-07 112 16 119
5.004_03 1997-Sep-05 109 0 17
5.004_04 1997-Oct-15 66 8 173
THE KEEPERS OF THE RECORDS
Jarkko Hietaniemi <jhi@iki.fi>.
Thanks to the collective memory of the Perlfolk. In addition to
the Keepers of the Pumpkin also Alan Champion, Andreas Knig, John
Macdonald, Matthias Neeracher, Michael Peppler, Randal Schwartz,
and Paul D. Smith sent corrections and additions.
--
Tom Christiansen tchrist@jhereg.perl.com
I am a little more weird today than normal. --Andrew Hume
------------------------------
Date: Wed, 6 May 1998 23:45:35 GMT
From: Eric Bohlman <ebohlman@netcom.com>
Subject: Re: How to compare to files
Message-Id: <ebohlmanEsK7Bz.KM3@netcom.com>
BrandSoft <brandsoft@aol.com> wrote:
: I am having a problem with my loops not working as I anticipated. The loop is
: below. I expect it to take each line of the first file and compare it to everl
: line of the second. It returns a pattern of ABABABABABAB or ABBBBBBBBB
: depending on my maipulationsa, but not the desired ABBBBBABBBBBABBBBB.
: $FILEIN = 'c:\mk\chktab\checktables.txt';
: $FILETEMPW = '>c:\mk\chktab\workfile.s1';
: $FILETEMPRO = 'c:\mk\chktab\workfile.s1';
: $FILEOUT = '>c:\mk\chktab\problem_tables.txt';
: $MASTER = 'c:\mk\chktab\alltable.master';
: open MASTER;
Why are you doing this here?
: open FILEOUT;
: open FILETEMPRO;
*Always* test to see if an attempt to open a file actually worked (this
isn't your problem now, but it could become one in the future).
: while ($origline=<FILETEMPRO>) {
This could terminate prematurely under some circumstances; better rewrite
it as:
while (defined($origline=<FILETEMPRO>)) {
: printf "A";
: open MASTER;
See above.
: while (<MASTER>) {
: printf "B";
: if ($origline = <MASTER>) {
Two problems here. First of all, '=' is an assignment operator, not a
comparison operator. You probably want 'eq' instead. Second, you're
skipping all the odd-numbered lines in MASTER; the first <MASTER> in your
loop conditional reads one line and stuffs it in $_; the second <MASTER>
in your if statement reads the next line and uses it in the comparison.
You probably want:
if ($origline eq $_) {
: print FILEOUT ($line);
Where did $line come from? If you had used the -w switch, perl would
have told you that you were using an uninitialized value. Be lazy and
let perl do some of your work for you. I can only guess at what you're
trying to print, but it's probably either $origline or $_.
: }
: close MASTER;
: }
: }
:
: close MASTER;
By the time you reach this point, MASTER has already been closed.
: close FILEOUT;
: close FILETEMPRO;
All that said, the algorithm you're using here is going to be extremely
slow if the files you're matching are of non-trivial size. If your
"tempro" file is N lines long and your master file is M lines long, your
program will have to do N*M comparisons, N*M file reads and N+1 file opens
and closes.
Fortunately, Perl has hashes, so there's a much faster way to do this.
Read the master file *once* and populate a hash with it. Then, for each
line in the "tempro" file, use it as a key to the hash and check if the
element exists. This gets you down to N comparisons (actually hash
lookups), N+M file reads and 2 opens and closes.
------------------------------
Date: 6 May 1998 23:20:11 GMT
From: mgjv@comdyn.com.au (Martien Verbruggen)
Subject: Re: IS THIS POSSIBE IN PERL!
Message-Id: <6iqr7b$fp1$3@comdyn.comdyn.com.au>
In article <6ipiq1$em4$1@news1.sol.no>,
tina@scandinaviaonline.se (Tina Marie Holmboe) writes:
> If, on the other hand, you *don't* know on which pages you link
> appear, and want to check *that* ... well, then the problem is a
> slightly different beast.
You could use Altavista to find a few :)
Martien
--
Martien Verbruggen |
Webmaster www.tradingpost.com.au | You can't have everything, where would
Commercial Dynamics Pty. Ltd. | you put it?
NSW, Australia |
------------------------------
Date: 6 May 1998 23:38:10 GMT
From: mgjv@comdyn.com.au (Martien Verbruggen)
Subject: Re: Localtime--dumb question probably
Message-Id: <6iqs92$fp1$7@comdyn.comdyn.com.au>
In article <6iogq2$ge9$1@nnrp1.dejanews.com>,
johnny99@sydney.dialix.oz.au writes:
> I'm using localtime in a script for a web form, to datestamp the emails it
> sends.
>
> I've got
>
> $timesent=localtime;
>
> and then
>
> print (SM $timesent);
What's SM? Why are you using print like this? Is SM a file handle you
opened or writing? In that case you should just do something like:
print SM $timesent;
# perl
$t = localtime;
print "$t\n";
^D
Thu May 7 09:36:15 1998
Nothing wrong with this.
Martien
--
Martien Verbruggen |
Webmaster www.tradingpost.com.au |
Commercial Dynamics Pty. Ltd. | Curiouser and curiouser, said Alice.
NSW, Australia |
------------------------------
Date: 5 May 1998 22:52:14 GMT
From: damian@cs.monash.edu.au (Damian Conway)
Subject: Re: Looking for Perl parser for 'C' language input files
Message-Id: <6io56u$ekj$1@towncrier.cc.monash.edu.au>
"James O. Payne, Jr." <jpayne@us.oracle.com> writes:
>I have a requirement to write a utility to do some not-so-simple
>search, modify, and replace type work on a large base of 'C' code.
>I wish to avoid lex and yacc due to the additional complexities that
>writing this utility in 'C' will add to my task.
You might like to check out the Parse::RecDescent module on the CPAN.
It provides most of the features of lex/yacc (and many more besides),
but in pure Perl.
AFAIK no-one has yet written a full C parser as a Parse::RecDescent grammar,
but it could certainly be done.
Damian
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
name: Damian Conway addr: School of Computer Science
email: damian@csse.monash.edu.au and Software Engineering
web: http://www.cs.monash.edu.au/~damian Monash University
fax: +61-3-9905-5146 Clayton 3168, AUSTRALIA
------------------------------
Date: Wed, 6 May 1998 22:44:07 GMT
From: Eric Bohlman <ebohlman@netcom.com>
Subject: Re: Open to suggestions
Message-Id: <ebohlmanEsK4HK.GCs@netcom.com>
Curtis Hoffmann <curtish@gte.net> wrote:
: On Tue, 05 May 1998 20:18:41 GMT, Tom Phoenix <rootbeer@teleport.com>
: wrote:
: >On Tue, 5 May 1998, Curtis Hoffmann wrote:
: >> What I'm asking for is pointers to a Perl script that can take a
: >> block of text data and store it to a particular subdirectory on the
: >> server.
: >
: >That's easy to do with Perl's file operations, of course.
: Not from what I can tell. There's TONS of information files,
: sample programs, books, etc. And most of this stuff is useless when
: the platform is Win32Perl. I'm spending more time wading through
: stuff I can't use, than I am in doing my real job (writing
: documentation for plasma etching equipment.)
That's strange; perl's file operations are for the most part
platform-independent; certainly the ones you'd need for your task are.
: >> The file names should be sequential, (i.e. - File0001.txt, File0002.txt,
: >> File0003.txt, etc.)
: >
: >That's easy to do, although there is a worry about concurrency. You may
: >need to use flock.
: Concurrency is not that important. The identifier data is being
: submitted within the forms data. The sequential names are just to
: prevent the script from overwriting an existing file before it's
: parsed by the PC application.
What do you mean by "concurrency is not that important"? Do you mean
that you can guarantee that only one user is submitting forms at a time?
Or do you mean that in your application, it's acceptable if two people
submit forms at the same time and they both get assigned the same
filename so that only actually gets stored? If the latter, what's the
point of the whole exercise?
------------------------------
Date: Wed, 06 May 1998 18:35:48 -0500
From: Beck Web Servers & Design <bwsd@bwsd.com>
To: btate@primary.net
Subject: Re: passing .htaccess login info
Message-Id: <3550E5C4.811660FC@bwsd.com>
Thanks Bob, I'll try to work something out with this. I don't know
exactly how, but I'll try...I assume the $id and $user_id are the main
one's I'd be interested in. This is new to me.
Eric
==========================
Bob Tate wrote:
>
> Eric,
>
> Here is a list of most of the Environment variables that are passed to the
> system. I run a secured site that requires authentication and use these
> variables to determine who the visitor is and what level of access they are
> allowed.
>
> # At this point we can get the local environment information
> # from the visiting user.
>
> $local = $ENV {'SERVER_NAME'} ;
> $remote = $ENV {'REMOTE_HOST'} ;
> $remote_ip = $ENV {'REMOTE_ADDR'} ;
> $server_sw = $ENV {'SERVER_SOFTWARE'} ;
> $server_pr = $ENV {'SERVER_PROTOCOL'} ;
> $user_sw = $ENV {'HTTP_USER_AGENT'} ;
> $port = $ENV {'SERVER_PORT'} ;
> $gateway = $ENV {'GATEWAY_INTERFACE'};
> $method = $ENV {'REQUEST_METHOD'} ;
> $language = $ENV {'HTTP_ACCEPT_LANGUAGE'};
> $id = $ENV {'REMOTE_IDENT'};
> $user_id = $ENV {'REMOTE_USER'} ;
> $path = $ENV{'PATH_TRANSLATED'} ;
------------------------------
Date: 6 May 1998 23:34:25 GMT
From: mgjv@comdyn.com.au (Martien Verbruggen)
Subject: Re: Problem installing Perl 5.004_04 on Solaris 2.5.1
Message-Id: <6iqs21$fp1$6@comdyn.comdyn.com.au>
In article <35504FCD.B7C4BE7A@pobox.com>,
Michael Peck <mpeck@pobox.com> writes:
> I have freshly installed Solaris 2.5.1 on a Sun Sparc 5. I have also
> installed all of the compilers and tools I can think of prior to
> installing Perl. When I try to make perl I get the following error
> messages:
>
> In file included from pp_sys.c:35:
> /usr/local/lib/gcc-lib/sparc-sun-sunos5.5/2.7.2.2/include/netdb.h:66:
> sys/bitypes.h: No such file or directory
> /usr/local/lib/gcc-lib/sparc-sun-sunos5.5/2.7.2.2/include/netdb.h:68:
> sys/cdefs.h: No such file or directory
> make: *** [pp_sys.o] Error 1
>
> From what I've discovered so far, it looks like 'bitypes.h' and
> 'cdefs.h' are both distributed with BIND 4.9.3. Why does perl require
> these when only a nameserver needs to run BIND?
For the gethost*, getnet* etc functions. See the perlfunc man page, section
'Fetching network info'
Martien
--
Martien Verbruggen |
Webmaster www.tradingpost.com.au | For heaven's sake, don't TRY to be
Commercial Dynamics Pty. Ltd. | cynical. It's perfectly easy to be
NSW, Australia | cynical.
------------------------------
Date: Wed, 06 May 1998 16:47:06 -0400
From: Dan Boorstein <danboo@negia.net>
Subject: Re: problem with cat
Message-Id: <3550CC4A.D2A36421@negia.net>
Ricky wrote:
>
> i'm trying to switch isp's and i'm having problem's getting the cgi
> stuff to work. here's the problem. i grabbed this from the mouse book
> a while back:
>
> sub cat{
>
> open (FILE, "/usr/bin/cat $_[0] |") || die "error opening pipe!";
>
> while (<FILE>) {
> print;
> }
>
> }
[SNIP]
>
> so i've been doing something like this. . .
>
> &cat("header.cat");
>
i think you're about to earn a "useless use of cat" award. why not just
open the file yourself. i think the example in the mouse was intended
to display the common errors in checking the status of pipe opens.
sub cat {
open (FILE, $_[0]) || die "$_[0]: $!";
while (<FILE>) {
print;
}
close FILE;
}
less typing, more portable, and your sub calls remain the same.
hope this helps,
--
Dan Boorstein home: danboo@negia.net work: danboo@y-dna.com
"THERE IS AS YET INSUFFICIENT DATA FOR A MEANINGFUL ANSWER."
- Cosmic AC
------------------------------
Date: 6 May 1998 22:58:00 GMT
From: ? the platypus {aka David Formosa} <dformosa@st.nepean.uws.edu.au>
Subject: Re: problem with cat
Message-Id: <894495480.664844@cabal>
In <3550C1A1.5AE7BE0@megsinet.net> Ricky <webmaster@apartmentzone.com> writes:
>i'm trying to switch isp's and i'm having problem's getting the cgi
>stuff to work. here's the problem. i grabbed this from the mouse book
>a while back:
>sub cat{
> open (FILE, "/usr/bin/cat $_[0] |") || die "error opening pipe!";
[...]
>. . . to grab headers and footers to build html pages on the fly.
>unfortunately, it doesn't work on the new server.
Could thay have cat in some place other then "/usr/bin/cat"? Also what
stops you from doing
open (FILE, "<$_[0]") or die "Help Help can't open file, where going
down";
while (<FILE>) {
print;
}
--
I'm a perl programer; if you need perl programing, hire me.
Please excuse my spelling as I suffer from agraphia; see the url. Support NoCeM
http://www.cit.nepean.uws.edu.au/~dformosa/Spelling.html http://www.cm.org/
I'm sorry but I just don't consider 'because its yucky' a convincing argument
------------------------------
Date: 06 May 1998 18:45:30 -0500
From: Jonathan Feinberg <jdf@pobox.com>
To: Mike Marziani <marz@tamu.edu>
Subject: Re: Problem with prune in File::Find
Message-Id: <yawfm09x.fsf@mailhost.panix.com>
Mike Marziani <marz@tamu.edu> writes:
> So I am wondering if anyone has heard of this and if someone who knows a
> bit about perl could check out that module and see if they can see if the
> prune command is indeed pruning too much.
Without seeing your code, the expected result, and the actual result,
it's impossible for us to guess what might be going wrong.
--
Jonathan Feinberg jdf@pobox.com Sunny Brooklyn, NY
http://pobox.com/~jdf/
------------------------------
Date: 6 May 1998 22:45:56 GMT
From: ? the platypus {aka David Formosa} <dformosa@st.nepean.uws.edu.au>
Subject: Re: References
Message-Id: <894494756.92908@cabal>
In <isaf8ve95c.fsf@godzilla.kiere.ericsson.se> Calle Dybedahl <qdtcall@esb.ericsson.se> writes:
[...]
>You can get the number of keys in a hash through a reference by
>evaluating %{$ref} in a scalar context.
No you will not, you will get a number like 7/128 telling you how
effective the hashing algorythum has been.
Evaluating c<keys %{$ref}> in a scalar context is more effective.
--
I'm a perl programer; if you need perl programing, hire me.
Please excuse my spelling as I suffer from agraphia; see the url. Support NoCeM
http://www.cit.nepean.uws.edu.au/~dformosa/Spelling.html http://www.cm.org/
I'm sorry but I just don't consider 'because its yucky' a convincing argument
------------------------------
Date: 6 May 1998 23:28:21 GMT
From: mgjv@comdyn.com.au (Martien Verbruggen)
Subject: Re: Script Needed: Referral/Affiliate/Commission reward script
Message-Id: <6iqrml$fp1$5@comdyn.comdyn.com.au>
In article <6il4lf$9a$1@gte1.gte.net>,
"James R. Thomson" <safepage@gte.net> writes:
> Script Needed: Pay commissions to sales as a result of a click on a
> banner
You might want to check www.cgi-resources.com to see if they have
anything you can use. Otherwise you'll have to pay someone to write
it. And it won't be a trivial task.
Martien
--
Martien Verbruggen |
Webmaster www.tradingpost.com.au | Very funny Scotty, now beam down my
Commercial Dynamics Pty. Ltd. | clothes.
NSW, Australia |
------------------------------
Date: 6 May 1998 23:12:59 GMT
From: mgjv@comdyn.com.au (Martien Verbruggen)
Subject: Re: Splain a regex to me
Message-Id: <6iqqpr$fp1$1@comdyn.comdyn.com.au>
In article <6ildbm$ul3$1@nnrp1.dejanews.com>,
rpearce@fastlane.net writes:
> In article <6ikjdn$u0j$1@nnrp1.dejanews.com>#1/1,
> kathryn.nelson@usa.net wrote:
>
>> i.e. /[ab].+:(\s*)/
>> "starts with the letter a or b followed by one or more characters followed
>> by a colon and zero or more whitespaces which are remembered as $1..."
>>
>
> I'm not positive, but the above would find the pattern whether it started with
> a or b, or if a or b started in the middle of the string.
>
> /^[ab].+:(\s*)/ would limit it to "starts with a or b".
>
> Right?
Semantics. The above definition holds true if you prepend
"The match " (starts with the ...)
In your case it would hold true for
"The string to match " (starts with ...)
Martien
--
Martien Verbruggen |
Webmaster www.tradingpost.com.au | In a world without fences, who needs
Commercial Dynamics Pty. Ltd. | Gates?
NSW, Australia |
------------------------------
Date: Wed, 06 May 1998 17:40:33 -0500
From: Bryan Hart <bryan@eai.com>
To: jen@personic.com
Subject: Re: Win32: Can't locate auto/Text/ParseWords/quotewords.al in @INC at exfld line 25
Message-Id: <3550E6E1.15FB@eai.com>
Nothing - those files appear to be missing from the ActiveWare install -
I fixed this by getting the native port and copying the correct files
into the install...
Bryan
donotspam-jen@personic.com wrote:
>
> I have no problem using quotewords on my RedHat Linux box, but when I try to
> run the same script under Win95 using ActiveState's perl, I get this error:
>
> Can't locate auto/Text/ParseWords/quotewords.al in @INC at exfld line 25
>
> Can anyone give me a tip on what I'm doing wrong?
>
> Thanks!
>
> Jen
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
--
------------------------------------------------------------
| Bryan Hart | Phone: (515) 296-5979 |
| Network Products Engineer | Fax: (515) 296-7025 |
| Engineering Animation Inc. | Email: bryan@eai.com |
| | WWW: http://www.eai.com/
|
------------------------------------------------------------
------------------------------
Date: 8 Mar 97 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 8 Mar 97)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.misc (and this Digest), send your
article to perl-users@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V8 Issue 2521
**************************************
