On Tue, 2004-06-22 at 11:03, Leopold Toetsch wrote:
> > More NCI definitions needed to make things pass on OS X.
> Thanks. I really shouldn't forget to update call_list.txt.
Would figuring out how to make the PPC JIT set up NCI calls help with
that?
Not particularly volunteering, just asking.
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> More NCI definitions needed to make things pass on OS X.
Thanks. I really shouldn't forget to update call_list.txt.
leo
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Tue, 22 Jun 2004, Leopold Toetsch wrote:
>> I think both should use just interpreter->class_hash. OTOH putting PMC
>> names into this one hash makes it more likely that we get name
>> collisions for user class names.
> Yeah. We probably ought to go rena
# New Ticket Created by Dennis Rieks
# Please include the string: [perl #30414]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=30414 >
Hi,
added just some missing files
cvsignore.patch:
RCS file: /cvs/public/parrot/.cv
On Friday 18 June 2004 03:56, Jonathan Worthington wrote:
> # New Ticket Created by Jonathan Worthington
> # Please include the string: [perl #30349]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=30349 >
>
>
> Hi,
>
> T
Michele Dondi writes:
> On Tue, 22 Jun 2004, Brent 'Dax' Royal-Gordon wrote:
>
> > > rename -v => 1, $orig, $new;
> >
> > It's already being done:
> >
> > rename $orig, $new :verbose;
> >
> > sub rename($orig, $new, +$verbose) {
> > say "Renaming `$orig' to `$new'" if $verb
On Tue, 22 Jun 2004, Brent 'Dax' Royal-Gordon wrote:
> > rename -v => 1, $orig, $new;
>
> It's already being done:
>
> rename $orig, $new :verbose;
>
> sub rename($orig, $new, +$verbose) {
> say "Renaming `$orig' to `$new'" if $verbose;
> ...
> }
I'm not sure
On Tue, 22 Jun 2004, Juerd wrote:
> Michele Dondi skribis 2004-06-22 18:24 (+0200):
> > rename -v => 1, $orig, $new;
>
> Any specific reason for the minus there? Perl's not a shell (yet).
Because one may want to restrict the number of pairs to be interpreted as
"cmd line" switches, I'm not ev
On Tue, 22 Jun 2004, greg strockbine wrote:
> my company would just love to embed
> the interpreter part of parrot into it's
> product (mtx603) that runs vxWorks.
Woohoo! That'd be cool.
> I'm trying to figure out if this is doable.
> I google'd the perl6-internals list but
> there's nary a ment
my company would just love to embed
the interpreter part of parrot into it's
product (mtx603) that runs vxWorks.
I'm trying to figure out if this is doable.
I google'd the perl6-internals list but
there's nary a mention of vxWorks.
a 'grep fork *.c' in the parrot source code
shows fork to occur o
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > On Tue, 22 Jun 2004, Leopold Toetsch wrote:
>
> >>old_limit = $P0."recursion_limit"(new_limit)
>
> > That's fine. We should add this (and anything else we do this way) to the
> > interpinfo op so the valu
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Tue, 22 Jun 2004, Leopold Toetsch wrote:
>>old_limit = $P0."recursion_limit"(new_limit)
> That's fine. We should add this (and anything else we do this way) to the
> interpinfo op so the values can be fetched back out, both by bytecode and
> via th
Juerd writes:
> Michele Dondi skribis 2004-06-22 18:24 (+0200):
> > rename -v => 1, $orig, $new;
>
> Any specific reason for the minus there? Perl's not a shell (yet).
>
> > rename.SWITCHES{-v} = sub {
> > my ($o, $n) = @_;
> > print "renaming `$o' to `$n'\n";
> > }
>
> I think
Michele Dondi wrote:
Specifically I'd like to have the possibility of doing something like
this:
rename -v => 1, $orig, $new;
It's already being done:
rename $orig, $new :verbose;
sub rename($orig, $new, +$verbose) {
say "Renaming `$orig' to `$new'" if $verbose;
...
Michele Dondi skribis 2004-06-22 18:24 (+0200):
> rename -v => 1, $orig, $new;
Any specific reason for the minus there? Perl's not a shell (yet).
> rename.SWITCHES{-v} = sub {
> my ($o, $n) = @_;
> print "renaming `$o' to `$n'\n";
> }
I think just using named arguments would be
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> We currently seem to have two different hashes for storing class names:
> one for PMC base classes and one for dynamic PMCs and objects.
>
> I think both should use just interpreter->class_hash. OTOH putting PMC
> names into this one hash makes it more
I know that it is probably (a few years) too late for a proposal like
this, that is highly "invasive" wrt Perl's semantic, but here it is
anyway...
Cmd line switches are so useful and effective to quickly change the
behaviour of programs: IIRC tcl's syntax was inspired by them. But OTOH it
is to
We currently seem to have two different hashes for storing class names:
one for PMC base classes and one for dynamic PMCs and objects.
I think both should use just interpreter->class_hash. OTOH putting PMC
names into this one hash makes it more likely that we get name
collisions for user class
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
>
> > For this case, I don't know if it matters much -- I don't know if there
> > are other platforms that don't define those macros -- but the general
> > principle of testing for features, not for platforms,
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> b1.py calls recursively functions, the depth is limited by the
> interpreter, which throws a RuntimeException at recursion depth 1000. So
> does Parrot now.
>
> The limit can be change by:
>
>$P0 = getinterp
>.local int new_limit
>.local in
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> For this case, I don't know if it matters much -- I don't know if there
> are other platforms that don't define those macros -- but the general
> principle of testing for features, not for platforms, is a good one and I
> like to jump up on my soapbox an
b1.py calls recursively functions, the depth is limited by the
interpreter, which throws a RuntimeException at recursion depth 1000. So
does Parrot now.
The limit can be change by:
$P0 = getinterp
.local int new_limit
.local int old_limit
new_limit = 4711
old_limit = $P0."recursion_lim
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> Pie-thon has Exception objects. We'll need such beasts too. So:
> 1) How do we "translate" Python classes? Properties only? Or
> full ParrotClass objects?
I think ParrotClass objects with properties should work fine.
Python objects are also refer
Pie-thon has Exception objects. We'll need such beasts too. So:
1) How do we "translate" Python classes? Properties only? Or
full ParrotClass objects?
2) We'll need to classify our exceptions somehow so that we can model an
exception class hierarchy. We'll also need to catch specific exceptions
Dennis Rieks <[EMAIL PROTECTED]> wrote:
> with this patch (and my previous stat.h patch) win32/vc6 compile, link and
> test now successfully (with system icu). See starshadow tinderbox log for
> more information.
Thanks, applied.
leo
On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> Dennis Rieks <[EMAIL PROTECTED]> wrote:
>
> > add this lines to config/gen/platform/generic/stat.h
>
> > I think that no win32/stat.[c|h] file is needed,
>
> I checked it in as config/gen/platform/win32/stat.h, which then gets
> included for win32. I'd
On Mon, 21 Jun 2004, Gregor N. Purdy wrote:
> So, where and when is the pie-throwing going to happen, precisely?
>
> IIRC, its at OSCON, but last time i googled for it, I didn't see
> mention of which OSCON session or BOF it would be at
The plan, last I knew, was to run the benchmarks at some
# New Ticket Created by Dennis Rieks
# Please include the string: [perl #30401]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=30401 >
Hi,
with this patch (and my previous stat.h patch) win32/vc6 compile, link and
test
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> There are a variety of places in the languages/ directory that require
> at least perl 5.006. This patch puts in 'require 5.006' in those files.
> If we later decide to make everything work with 5.005, these will at least
> mark some of the problem spot
Dennis Rieks <[EMAIL PROTECTED]> wrote:
> add this lines to config/gen/platform/generic/stat.h
> I think that no win32/stat.[c|h] file is needed,
I checked it in as config/gen/platform/win32/stat.h, which then gets
included for win32. I'd like to keep things separate.
leo
30 matches
Mail list logo
