Ben Morrow wrote:
...but that's just a braino on Matt's part, and his point still stands
for the code
package Test;
sub apply {
my $func = shift;
$func->(shift) while @_;
}
package Foo;
use vars qw/$line/; # can't use our as that also creates a lexical
Matt Diephouse wrote:
Let's try this again, starting from the Tcl side of things. Tcl code
can exist outside of subroutines. This, for example, is a valid Tcl
program:
set number 5
puts $number
[...]
But things get a
little hairier when we start using namespaces in Tcl:
namespace eval t
On Wednesday 22 November 2006 16:04, James E Keenan wrote:
> And now, a question about how the Parrot Makefile utilizes pmc2c.pl ...
>
> The Makefile calls:
>
>PMC2CD = $(PERL) $(BUILD_TOOLS_DIR)/pmc2c.pl --dump
>
> ... which inside pmc2c.pl translates into:
>
>dump_pmc([EMAIL PROTECTED],
And now, a question about how the Parrot Makefile utilizes pmc2c.pl ...
The Makefile calls:
PMC2CD = $(PERL) $(BUILD_TOOLS_DIR)/pmc2c.pl --dump
... which inside pmc2c.pl translates into:
dump_pmc([EMAIL PROTECTED], @ARGV);
What kind of files does the Makefile place in @ARGV?
I need to fi
Quoth [EMAIL PROTECTED] (Allison Randal):
> Matt Diephouse wrote:
> >
> > Consider the following Perl 5 code:
> >
> > package Test;
> > sub apply {
> > my $func = shift;
> > $func->(shift) while @_;
> > }
> > package Foo;
> > my $line = 0;
> > my $func = sub { print $line++, " ",
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #40972]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40972 >
Hi,
in t/pmc/env.t I noticed that an Iterator test is skipped under Win23:
Am Mittwoch, 22. November 2006 21:03 schrieb Leopold Toetsch:
> Am Mittwoch, 22. November 2006 18:03 schrieb Patrick R.Michaud:
> > Is this a bug (I think it is), or does the underscore in
> >
> > :multi mean something other than "any argument"?
>
> The meaning is 'any PMC' [1], and it of course ca
Am Mittwoch, 22. November 2006 18:03 schrieb Patrick R.Michaud:
> Is this a bug (I think it is), or does the underscore in
>
> :multi mean something other than "any argument"?
The meaning is 'any PMC' [1], and it of course can't be a bug as there are no
specs ;)
leo
[1] multi_type:
compilers/i
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #40966]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40966 >
---
osname= linux
osvers= 2.6.16
arch= x86_64-linux-thread-multi
cc= cc
---
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #40968]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40968 >
I'm filing this as a bug report, but it could just be that
I don't understand how
chromatic wrote:
On Tuesday 21 November 2006 18:36, James E Keenan wrote:
3 identically named subroutines: 2 in modules and 1 in a script. And
all 3 will be in modules as I'm planning to refactor much of pmc2c.pl
into a module called Parrot::Pmc2c::Utils. (For drafts of these
revisions, se
Let's try this again, starting from the Tcl side of things. Tcl code
can exist outside of subroutines. This, for example, is a valid Tcl
program:
set number 5
puts $number
In order to compile this to PIR, we have to put it into a subroutine.
The only problem with putting it into a subroutine i
12 matches
Mail list logo
