I read Audrey's Tang blog and some things it linked to. Great stuff. I
learned that *.pmc files have precedence over *.pm files. Does this introduce
a security issue, i.e. anything new beyond the existing risks? I wonder if an
evil *.pmc file might not even be noticed when searching for a
hi
some thoughts came to mind after listening to audrey's talk.
what reasons are there to use perl 6?
what can it do that i can't do with with X language?
why write something using perl 6?
[and we can skip the stuff about whether it's production ready or not-
that is valid for all software
On Fri, Jul 14, 2006 at 08:29:52AM -0400, Tolkin, Steve wrote:
I read Audrey's Tang blog and some things it linked to. Great stuff.
I learned that *.pmc files have precedence over *.pm files. Does this
introduce a security issue, i.e. anything new beyond the existing
risks? I wonder if an
what reasons are there to use perl 6?
Many possible reasons ...
* Masochistic desire to be an alpha tester.
* Starting a new project that will be maintained well into the Perl 6
era, writing it with use v6; style may lower maintenance costs later
after your maintenance programmers are P6
Specifically, can the *.pmc file be in a different directory than the
*.pm file that was intended to be used?
If it were implemented exactly as Audrey said, it would -- if checking
for $Module.pmc first, then for $Module.pm , which doubles the number
of fstats to (upto) 2*scalar @INC.
On Fri, Jul 14, 2006 at 09:33:14AM -0400, Bill Ricker wrote:
Specifically, can the *.pmc file be in a different directory than
the *.pm file that was intended to be used?
If it were implemented exactly as Audrey said, it would -- if checking
for $Module.pmc first, then for $Module.pm ,
I hope we're not starting a flamewar here... Note that I'm not going to
irrationally bash Perl 6 here (despite my past record about it). Read on for
the rest of my reply.
On Friday 14 July 2006 15:46, [EMAIL PROTECTED] wrote:
hi
some thoughts came to mind after listening to audrey's talk.
On Fri, Jul 14, 2006 at 09:40:18AM -0400, Dan Boger wrote:
And strace shows it does chech for a .pmc in every member of @INC:
...
stat64(/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/5.8.5/i386-linux-thread-multi/Data/Dumper.pmc,
0xbff9c830) = -1 ENOENT (No such file or
From: Ronald J Kimball [EMAIL PROTECTED]
Date: Thu, 13 Jul 2006 17:57:20 -0400
34 people came to Tuesday's tech meeting!
I'm afraid I have an unfortunate postscript to add. I attended the
meeting with a mysterious rash on my chest, which turned out to be
herpes zoster, a.k.a. shingles:
Hi Bob,
From the speaker's 180-degree panoramic view, where were you seated?
Bob Xiong
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Bob Rogers
Sent: Friday, July 14, 2006 11:49 AM
To: Ronald J Kimball; Audrey Tang; Boston Perl Mongers
On 14 Jul 2006, [EMAIL PROTECTED] wrote:
What other P6 features are considered big win motivators to start
using P6 by others?
I think the new grammar feature (to me, it's very similar to what
Parse::RecDescent does today, but P::RD has problems and it's slow as
noted by others) is going to
Summary: How to use Perl 5.8.0 to handle files encoded using utf-16 on
Windows?
Details:
I have read that perl 5.8 ought to handle utf-16 without me needing to
tell it anything.
But I am now getting the behavior I expect.
Specifically, I want to find what changed in a Registry after I install
a
From: Tolkin, Steve [EMAIL PROTECTED]
Date: Fri, 14 Jul 2006 16:51:04 -0400
Summary: How to use Perl 5.8.0 to handle files encoded using utf-16 on
Windows?
Details: . . .
How about trying to re-encode it as UTF-8 first? This should at least
give you some compression of the
13 matches
Mail list logo
