On Wed, 14 Aug 2002, Luke Palmer wrote:
> Why? We could make arglists exactly equivilent to the way they're done in
> Perl 5, which is a good way.
>
> sub foo($a, $b, *@c) {...}
>
> Would be exactly equivilent to Perl 5's
>
> sub foo { my ($a, $b, @c) = @_; ... }
I've got anothe
Hi,
when testing native types with perl6 I encountered the following problem:
..p6:
my $b is Boolean = 2;
..imc:
.local Boolean _SV_b1
$P4 = new PerlUndef
$P4 = 2
_SV_b1 = $P4
..pasm:
new P14, .PerlUndef
set P14, 2
set P10, P14
..pbc
new_p_ic P14,2
s
Hi,
assembler.pl has it's private (propably handmade) list of PMC types.
lib/Parrot/PMC.pm is exactly this list, generated by pmc_pm.pl.
Is there any reason why
- PMC.pm is generated with \Lowercased names
- and assemble.pl can't use it?
leo
Leopold Toetsch wrote:
> new P14, .PerlUndef
> set P14, 2
> set P10, P14
> An more generally, shouldn't set_p_p call some vtable function?
No. set Px, Py simply sets the Px register to point to the same PMC
as Py already points to; it does not care about the content of the
PMC in any way. The
On Thu, 15 Aug 2002, Deven T. Corzine wrote:
: I've got another idea. How about using a copy-restore technique?
I suspect that would make Perl 6's sub calls even slower than Perl 5's.
Larry
On Thu, 15 Aug 2002, Larry Wall wrote:
> On Thu, 15 Aug 2002, Deven T. Corzine wrote:
> : I've got another idea. How about using a copy-restore technique?
>
> I suspect that would make Perl 6's sub calls even slower than Perl 5's.
Yes and no.
For the normal case (pass-by-value semantics), it
On Mon, Aug 12, 2002 at 12:37:09AM -0700, Sean O'Rourke wrote:
> What Dan says. If you're interested, there are at least three options:
>
> - a fairly well-developed compiler for perl 5 regexes (languages/regex).
>
> - a less well-developed compiler built into the prototype Perl 6 compiler
>
Peter Gibbs wrote:
[ set_p_p ]
> ... The future 'assign Px, Py' will call a vtable function
> (set_pmc);
So, trying to set a Boolean to "2", would be a case for the proposed
"assign" function, ok, yes.
> ... however, in the quoted example, the pure register level
> behaviour is all that is
Sorry for replying myself,
> my $b is Boolean = 2;
Here obviously a syntax disorder slept in, but the conclusion would be
the same.
leo
Leopold Toetsch wrote:
> I currently can't imagine any useful RL example for the current
> implementation of set_p_p as $1=$2, _if_ the involved PMC types are
> different.
You need to differentiate between the PMC itself, and a Parrot register
that holds the address of a PMC. In the instructio
On Thu, 15 Aug 2002, Deven T. Corzine wrote:
> On Thu, 15 Aug 2002, Larry Wall wrote:
>
> > On Thu, 15 Aug 2002, Deven T. Corzine wrote:
> > : I've got another idea. How about using a copy-restore technique?
> >
> > I suspect that would make Perl 6's sub calls even slower than Perl 5's.
>
> Y
On Wed, Aug 14, 2002 at 03:16:20AM -0400, Mike Lambert wrote:
> > If the rx info object is going away, then obviously those parts of the
> > patch need not be applied. But in the meantime, it's nice to have a
> > Parrot that doesn't crash.
>
> I agree. My disclaimer about the regex code in my ori
# New Ticket Created by Jason Gloudon
# Please include the string: [perl #16237]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16237 >
This provide register window flushing code for sparc, for both 32-bit and
64-bit CPUs
13 matches
Mail list logo
