On 3/17/06, David Golden <[EMAIL PROTECTED]> wrote:
> Adam Kennedy wrote:
> > The only problem with this is that it only deals with CPAN.pm itself.
> >
> > The problem with locked files is wider than this.
> >
> > Imagine for example that you have Windows mod_perl or some other
> > long-running pro
demerphq wrote:
The point i was making is that it isnt actually necessary for Schwern
to do anything for you to enjoy the benefits of the new Install code.
> [snip]
cpan> install YVES/ex-ExtUtils-Install-1.3701.tar.gz
the you are cooking, with gas, right now. :-)
That's great, but I want e
Author: pmichaud
Date: Thu Mar 16 18:44:22 2006
New Revision: 11914
Modified:
trunk/docs/pdds/pdd03_calling_conventions.pod
Log:
"Paramters" -> "Parameters"
Modified: trunk/docs/pdds/pdd03_calling_conventions.pod
==
I'm trying to capture coverage data for a large project I'm working on. I'm
running all of my unit tests through Test::Harness and I'm trying to utilize
Devel::Cover within the harness. Honestly this is mostly a nitpicky thing
because I can get Devel::Cover to work, but I'm seeing warnings and I wa
Hi Mr. Gianni!
I don't know what is the solution to your problem, but I'd like to make a
general netiquette note. Please don't start a new thread by replying to an
existing message from the list. That's because that way, thread-aware mailers
display it as a reply to the message.
Instead, write
Just a quick note that in r11916 I've updated PGE's
internal attribute names to match the new secondary
sigils identified by S12. Thus, @:capt is now @!capt,
&:corou is now &!corou, etc.
(For the pugs folks, I updated the Hs.pir file as well.)
This shouldn't have much of an impact on anyone usi
Fixed, finally.
On Mar 16, 2006, at 5:40 AM, Alberto Simoes wrote:
Cheers
Alberto
Author: pmichaud
Date: Fri Mar 17 08:05:47 2006
New Revision: 8328
Modified:
doc/trunk/design/syn/S12.pod
Log:
Typo fix: "In Perl 6 gives you a choice." -> "Perl 6 gives you a choice."
Modified: doc/trunk/design/syn/S12.pod
On 3/17/06, chromatic <[EMAIL PROTECTED]> wrote:
>
> Do you mean that it's valuable only for the author to run (perhaps during
> disttest) and rarely useful for the user to run during installation?
Aye. Though I can imagine users who'd like to run them as well... This is
after all not that differ
On Mar 11, 2006, at 2:07, Nicholas Clark wrote:
I feel more comfortable with the idea of IO being methods on PMCs
than raw
OPs.
They are methods on I/O objects internally. (Just as most opcodes on
PMCs actually call vtable methods.) So, the question isn't as
significant as it appears. I
Author: larry
Date: Fri Mar 17 15:41:25 2006
New Revision: 8336
Modified:
doc/trunk/design/syn/S11.pod
Log:
Fixes from Damian
Clarification of default Perl package name
Clarification of when we need not default to Perl 5
Modified: doc/trunk/design/syn/S11.pod
I've just applied a change (r11921) to PGE that allows
embedded closures in rules to designate a "return value" for
a match (recently added to S05).
Essentially this means that a rule such as
/:lang(PIR) foo {{ .return "bar" }} /
will match a string containing "foo" but gives the returned ma
On Mar 3, 2006, at 15:54, Joshua Isom wrote:
Concerning all the byte/character issues, all the string opcodes
except bytelength work with characters. But the io subsystem
currently only deals with bytes. I know there is the speed issue
for things like reading with dealing with utf8, but
On Fri, Mar 17, 2006 at 07:08:55PM -0600, Patrick R. Michaud wrote:
> I've just applied a change (r11921) to PGE that allows
> embedded closures in rules to designate a "return value" for
> a match (recently added to S05).
> [...]
I neglected to mention in my previous post that this update
seems t
Audrey Tang wrote:
On 3/17/06, chromatic <[EMAIL PROTECTED]> wrote:
Do you mean that it's valuable only for the author to run (perhaps during
disttest) and rarely useful for the user to run during installation?
Aye. Though I can imagine users who'd like to run them as well... This is
after
On Mar 6, 2006, at 4:06, Nicholas Clark wrote:
On Fri, Mar 03, 2006 at 11:27:05AM -0800, Allison Randal wrote:
=head2 Network I/O Opcodes
Functionality wise, the following are missing:
shutdown
Added.
getpeername/getsockname
getsockopt/setsockopt
These seem rare, and intimatel
I just committed a more complete draft of the I/O PDD to docs/pdds/
clip/pddXX_io.pod. I've integrated or responded to the mailing list
comments. I also added a good bit of additional discussion of
asynchronous operations and error handling. The original draft was
"how it works now", while t
From my understanding, one of the little idiosyncrasies of
Makefile.PL/Build.PL installers (including MI variants of both) is that
in order to make sure that the Makefile and Build use the correct perl
installation, you should always be explicitly running M/B.PL with the
perl you want to instal
18 matches
Mail list logo
