Leopold Toetsch wrote:
The Perl 6 Summarizer <[EMAIL PROTECTED]> wrote:
It turned out to be a simple matter of unimplemented functions,
which he and Leo rapidly implemented.
s/he and Leo/he/
I was just the one hitting Ctrl-C Ctrl-V. (Actually, I was using the
mouse, since I was working
The Perl 6 Summarizer <[EMAIL PROTECTED]> wrote:
> Good news! Bad news!
> Good news! Dan says the infrastructure is in place to do delegated
> method calls for vtable functions with objects. Bad news! It doesn't
> actually work
That's solved already. You can override e.g. "inc Px" w
Sorry, typo- I have no idea how that got by.
--Josh
At 5:00 on 03/09/2004 +0100, Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Tuesday 09 March 2004 04:24, Josh Wilmes wrote:
> > cvsuser 04/03/08 19:24:12
> >
> > Modified:src interpreter.c
> > Log:
> > Missing function/d
Hi,
On Tuesday 09 March 2004 04:24, Josh Wilmes wrote:
> cvsuser 04/03/08 19:24:12
>
> Modified:src interpreter.c
> Log:
> Missing function/data casts.
>
> Revision ChangesPath
> 1.279 +3 -3 parrot/src/interpreter.c
>
> Index: interpreter.c
> ==
On Mon, Mar 08, 2004 at 11:57:04PM +, Dave Mitchell wrote:
: On Sat, Mar 06, 2004 at 06:39:44PM -0800, Larry Wall wrote:
: > my @x will begin {...} # at BEGIN time
: > my @x will check {...} # at CHECK time (redefined to unit check)
: > my @x will init {...} # at INI
On Sat, Mar 06, 2004 at 06:39:44PM -0800, Larry Wall wrote:
> my @x will begin {...} # at BEGIN time
> my @x will check {...} # at CHECK time (redefined to unit check)
> my @x will init {...} # at INIT time
> my @x will end {...}# at END time
Sorry, perhaps
At 11:04 PM +0100 3/8/04, Sebastian Riedel wrote:
Dan Sugalski wrote:
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
Can we add a caption to the output? Otherwise I'll end up forgetting.
Will be added in the next version.
Cool, thanks.
We also need to implement a me
The Perl 6 Summary for the week ending 2004-03-07
Time marches on, and another summary gets written, sure as eggs are eggs
and chromatic is a chap with whom I will never start a sentence. We
start, as always, with perl6-internals.
Platform games
Work continued this week on expand
Le lundi 08 mars 2004 à 22:44, Paul Johnson écrivait:
>
> Probably the most important change is that Devel::Cover will now work
> with programs that turn on tainting. I gather this is important for
> Phalanx. Hi Andy!
>
Does Devel::Cover work with programs/modules that fork a lot?
I tried to
Dan Sugalski wrote:
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2
> Probably the most important change is that Devel::Cover will now work
> with programs that turn on tainting. I gather this is important for
> Phalanx. Hi Andy!
Test::Harness is now more happy, but not entirely so, at running under
Devel::Cover. I'll investigate more tonight.
Thanks for the u
> Probably the most important change is that Devel::Cover will now work
> with programs that turn on tainting. I gather this is important for
> Phalanx. Hi Andy!
Never mind Phalanx, I'd just like to run Test::Harness under it!
I'll let you know what I find!
--
Andy Lester => [EMAIL PROTECTED]
>From the CHANGES file:
- Change Text2 to pick up version changes.
- Minor documentation updates.
- Minor changes to Devel::Cover::Op.
- Add outputfile option to HTML output (David Wheeler).
- Document -silent option to Devel::Cover.
- Add -silent option to cover (David Wheeler).
- Make Dev
At 10:10 PM +0100 3/8/04, Sebastian Riedel wrote:
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2 100%40% 22%
Abhijit A. Mahabal wrote:
A very basic newbeish question..
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
oo1 100%39% 23% -
oo2 100%40% 22% -
Are bigger numbers more desirable
A very basic newbeish question..
> >
> >>[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
> >>../parrotbench.conf
> >>parrot perlpython ruby
> >>oo1 100%39% 23% -
> >>oo2 100%40% 22% -
> >>
Are bigger numbers more desirable (as the
Leopold Toetsch wrote:
Sebastian Riedel <[EMAIL PROTECTED]> wrote:
Sebastian Riedel wrote:
The attached version should do most of the things you wanted.
[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
../parrotbench.conf
parrot perlpython ruby
I've been thinking about vtable and opcode functions written in
bytecode, and I think that we need an alternate form of sub calling.
(And yes, this *is* everyone's chance to say "I told you so")
The current calling conventions are optimized for the case where the
caller knows that that a call i
Hi,
On Monday 08 March 2004 16:40, Leopold Toetsch wrote:
> Jens Rieks <[EMAIL PROTECTED]> wrote:
> >> $P0 = new Foo
> >
> > This is wrong. Use $P0 = new "Foo" instead.
>
> No. There isn't even such an opcode. Above code is fine and working,
> because during compilation of "loadlib", the c
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Nope, we don't need it. We can go one less level of indirection than
> List, too, since we don't need the info it provides either, as the
> entries are guaranteed to be PMCs. We can hang a bare PMC buffer
> (well, OK, PArray, but they should be the same th
Jens Rieks <[EMAIL PROTECTED]> wrote:
>> $P0 = new Foo
> This is wrong. Use $P0 = new "Foo" instead.
No. There isn't even such an opcode. Above code is fine and working,
because during compilation of "loadlib", the class file gets already
loaded so that the type is registered. This might c
At 12:03 PM -0500 3/7/04, Simon Glover wrote:
Which leads me to ask a question that I've been pondering for a while
-- do we actually need to use a fullblown Array PMC to hold the object
meta-information and attributes? Couldn't we save a level of indirection
(and one PMC header per object) by
Ilya Martynov <[EMAIL PROTECTED]> wrote:
> Patch below my signature is required to allow to run classes/pmc2c2.pl
> from any directory. Otherwise it will complain it cannod find .dump
> files unless it is being run from parrot directory.
Thanks, applied.
leo
Ilya Martynov <[EMAIL PROTECTED]> wrote:
> 1. find_method crashes parrot when used with dynclasses
Fixed.
> 2. Why following code emits "Method 'find_method' not found"?
>Shouldn't find_method be defined in vtable of Boolean PMC?
> .sub main
> $P0 = new Boolean
> find_method
Hi again,
(small note for little jens: first read _everything_, then write an answer,
then read it and send it afterwards...)
> On Monday 08 March 2004 13:33, Ilya Martynov wrote:
> > # New Ticket Created by Ilya Martynov
> > # Please include the string: [perl #27504]
> > # in the subject lin
Hi,
On Monday 08 March 2004 14:26, Morten Sickel wrote:
> I don't know if it is of any interest, I just found HP-UX mentioned, but I
> have just tested parrot 0.0.10 on HP-UX 10.20 / gcc 3.2 all tests passed
> (I'll start testing 0.0.11 tomorrow)
0.1.0 is the latest version.
Please look at the new
Hi,
On Monday 08 March 2004 13:33, Ilya Martynov wrote:
> # New Ticket Created by Ilya Martynov
> # Please include the string: [perl #27504]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=27504 >
>
>
>
> 1. find_method
# New Ticket Created by Ilya Martynov
# Please include the string: [perl #27504]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27504 >
1. find_method crashes parrot when used with dynclasses
For example if I build Foo
# New Ticket Created by Ilya Martynov
# Please include the string: [perl #27505]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27505 >
Patch below my signature is required to allow to run classes/pmc2c2.pl
from any dir
I don't know if it is of any interest, I just found HP-UX mentioned, but I
have just tested parrot 0.0.10 on HP-UX 10.20 / gcc 3.2 all tests passed
(I'll start testing 0.0.11 tomorrow)
regards
Morten
--
Morten Sickel
Norwegian Radiation Protection Authority
tel (47) 67162608
http://www.nrpa.no
Ibotty <[EMAIL PROTECTED]> wrote:
> just catched up mail and thought a bit practice might not be bad...
> i intentionally did not wrote them optimal (performance-wise), but rather
> elegantly (sort of ;).
Yeah, that's always the problem. Where applicable, we could add a set of
optimized versions
Sebastian Riedel <[EMAIL PROTECTED]> wrote:
> The attached version should do most of the things you wanted.
I've now added parrotbench.pl (slightly modifed) to the CVS tree.
thanks,
leo
leo wrote:
> Any one out there, who speaks ruby and can translate tests, for which
> we have a '.pl' file?.
just catched up mail and thought a bit practice might not be bad...
i intentionally did not wrote them optimal (performance-wise), but rather
elegantly (sort of ;).
thus this is only a perf
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #27486]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=27486 >
2004-Mar-07
Objective:
The classes/pmc_*.h C API's are supposed to be visible
[Gordon == [EMAIL PROTECTED] on Wed, 3 Mar 2004 16:48:45 -0500]
Gordon> gmclock(out Nx)
Gordon> UTC clock in seconds since hrs Jan 1, 2000,
Gordon> ignoring leap seconds.
Gordon> tolocal out Nx, out Iy, in Nz
Gordon> x is set to z converted to the local time z
Sebastian Riedel <[EMAIL PROTECTED]> wrote:
> Sebastian Riedel wrote:
> The attached version should do most of the things you wanted.
> [EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
> ../parrotbench.conf
> parrot perlpython ruby
> oo1 100%39% 23%
36 matches
Mail list logo
