Mailing List Archive

> http://mox.perl.com/
>
> check it out and tell me what else the perl area should
> mention.

Suggestion:

Start with a line or three about what perl is, and what perl5 is.
Remember that the reader can be anything from a novice (so novice that
he shouldn't look at perl yet) and up.

Then split it in sections: For common mortals (FAQ, source for plain
5.001m, and maybe the Single Recommended Place to look for extentions),
a section or more with the rest.


Regards,

Hallvard

> > http://mox.perl.com/
> >
> > check it out and tell me what else the perl area should
> > mention.

> Suggestion:

> Start with a line or three about what perl is, and what perl5 is.
> Remember that the reader can be anything from a novice (so novice that
> he shouldn't look at perl yet) and up.

> Then split it in sections: For common mortals (FAQ, source for plain
> 5.001m, and maybe the Single Recommended Place to look for extentions),
> a section or more with the rest.

those are good ideas. i hope to do that one of these days, but
i'm a little overworked right now.

btw, the perl bugs html stuff has been requested to be made the perl 5
bugs stuff because "so many people can only use perl4". i'll mention it
as such, but my formal position happens to be casual disinterest if not
disdain, which is probably rude, but i can't see how we can be in the
position of supporting ancient code when fixes are available.

btw, i spent several hours working with a company who wants to install
perl5, but they have so much internal stuff that breaks miserably due
to

system "mail $user@localhost"

type boggosities that they're thinking of hacking on the perl5 src
itself to regress to the old broken behaviour. sigh.

--tom

>>>>> "Tom" == Tom Christiansen <tchrist@mox.perl.com> writes:

Tom> btw, i spent several hours working with a company who wants to install
Tom> perl5, but they have so much internal stuff that breaks miserably due
Tom> to

Tom> system "mail $user@localhost"

Tom> type boggosities that they're thinking of hacking on the perl5 src
Tom> itself to regress to the old broken behaviour. sigh.

One good

perl -pi.bak -e 's/([^\\])\@localhost/\1\\\@localhost/' *.pl

oughta fix it. :-)

Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@ora.com)
Web: <A HREF="http://www.teleport.com/~merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me

> Tom> btw, i spent several hours working with a company who wants to install
> Tom> perl5, but they have so much internal stuff that breaks miserably due
> Tom> to

> Tom> system "mail $user@localhost"

> Tom> type boggosities that they're thinking of hacking on the perl5 src
> Tom> itself to regress to the old broken behaviour. sigh.

> One good

> perl -pi.bak -e 's/([^\\])\@localhost/\1\\\@localhost/' *.pl

> oughta fix it. :-)

except that it's not always @localhost nor in a dot pl file.

i've suggested a find and a perl5 -wc on all resulting scripts,
but that STILL won't catch the evals (they're way too big on
evals) and since it's a production system, they can't afford
any mistakes. i believe they'll never upgrade.

--tom