Okay, languages/perl6 is failing all its tests.
The problem is in a few recent changes to lib/Parrot/Test.pm. The Perl
6 test module in languages/perl6/P6C/TestCompiler.pm inherits from
Parrot::Test, but overrides some subs. P6C::TestCompiler's
&generate_pbc_for is writing the .pasm files in subdi
On Apr 20, 2004, at 3:06 PM, Leopold Toetsch wrote:
hyper
Px += 4 # add 4 to each column in data base
How does this look in pasm? Is it supposed to be:
hyper
add P0, 4
or is it:
hyperadd P0, 4
If it's the former, it seems really odd to have an op which modifies
the meani
Jeff Clites <[EMAIL PROTECTED]> wrote:
> The attached patch adds 2 Configure.pl options, to help with the
> process of getting ICU to build on platforms which are having
> difficulties with it:
Thanks, applied.
leo
Jeff Clites wrote:
On Apr 20, 2004, at 3:06 PM, Leopold Toetsch wrote:
hyper
Px += 4 # add 4 to each column in data base
How does this look in pasm? Is it supposed to be:
hyper
add P0, 4
Exactly that.
If it's the former, it seems really odd to have an op which modifies the
meani
Dan Sugalski wrote:
So, parrotcode.org's getting a bit crusty in its content (though with
a spiffy-keen new look if you've not looked in a while) and we need to
fix that.
Rather than putting this on my essentially infinitely long todo list,
this'd be a good spot for someone who wants to get in
role A {has Cat $.x;}
role B {has Dog $.x;}
class Foo {does Cat; does Dog;}
my Foo $bar;
$bar.x; # Is this a Cat or a Dog?
=
Jonathan "Dataweaver" Lang
__
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http:/
How would I call attributes? Specifically, what if I'm calling a list
attribute from a scalar object?
my Dog $spot;
my Dog @pack;
$spot->@.legs; # INCORRECT (I hope)
[EMAIL PROTECTED]; # INCORRECT?
@spot.legs;# What if you also have @spot declared?
=
Jonathan "Dataweaver" L
> -Original Message-
> From: Larry Wall [mailto:[EMAIL PROTECTED]
>
> On Tue, Apr 20, 2004 at 03:53:31PM -0400, Aaron Sherman wrote:
> : In specific, here is a proposal for execution:
> :
> : multi run(string $command) returns(Process) {...} # Funky shell default
> : multi run(Pro
> -Original Message-
> From: Jonathan Lang [mailto:[EMAIL PROTECTED]
>
> role A {has Cat $.x;}
> role B {has Dog $.x;}
> class Foo {does Cat; does Dog;}
> my Foo $bar;
> $bar.x; # Is this a Cat or a Dog?
If, however, two roles try to introduce a method of the same name (for some
defini
Jonathan Lang wrote:
How would I call attributes? Specifically, what if I'm calling a list
attribute from a scalar object?
my Dog $spot;
my Dog @pack;
$spot->@.legs; # INCORRECT (I hope)
[EMAIL PROTECTED]; # INCORRECT?
@spot.legs;# What if you also have @spot declared?
As a gues
I've put in another ICU config patch that adds these 2 options to
Configure.pl:
--icuheaders=(header_dir) Location of headers w/o /unicode
--icushared=(linkeroption)> Full linker command
Here is a sample (line-wrapped) Configure line:
perl Configure.pl --icushared='-L /opt/openoffice/pr
Allison Randal <[EMAIL PROTECTED]> wrote:
> Will or Jerome, could you take a minute to explain the direction you're
> taking Parrot::Test? I'll patch P6C::TestCompiler to match the new
> setup, but I want to do an "architecture sanity check" first.
I'd rather have the test files back in our tree.
On Tue, Apr 20, 2004 at 04:30:42PM -0400, Dan Sugalski wrote:
: At 4:20 PM -0400 4/20/04, Aaron Sherman wrote:
: >On Tue, 2004-04-20 at 11:53, Dan Sugalski wrote:
: >
: >> Y'know... let's just go all the way with this, since we're going to have
: >> to.
: >>
: >> We'll add a hyper version of all t
# New Ticket Created by WOOLLEY kj
# Please include the string: [perl #29024]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29024 >
Not a biggie, but here is a quick patch for ops.num that should stop
the warnings abou
On Tue, Apr 20, 2004 at 10:51:04PM -0700, Larry Wall wrote:
>
> Yes, that's in the works. The plan is to have four Unicode support levels.
> These would be declared by lexically scoped declarations:
>
> use bytes 'ISO-8859-1';
> use codepoints;
> use graphemes;
> use letters 'Tu
Woolley Kj <[EMAIL PROTECTED]> wrote:
> Not a biggie, but here is a quick patch for ops.num that should stop
> the warnings about ops 1426 to 1432 not being mentioned there.
It's not really decided, if these opcodes are 'official'. So I'd rather
wait a bit before nailing down ops.num.
> Che
Jeff Clites <[EMAIL PROTECTED]> wrote:
> Here's another tiny patch, to let us fast-fail string_equal if we have
> cached hashval's which don't match.
Tested and applied now. I've also adoped JIT/i386 to use string_equal
for C and C string ops. This speeds up these ops considerably
*and* in the ca
Originally sent to Austin alone by accident
Austin Hastings wrote:
-Original Message-
From: Jonathan Lang [mailto:[EMAIL PROTECTED]
role A {has Cat $.x;}
role B {has Dog $.x;}
class Foo {does Cat; does Dog;}
my Foo $bar;
$bar.x; # Is this a Cat or a Dog?
If, however, two roles try
I was asked to post a small summary of hyper ops for you guys. Here it
is:
Of course to hyperize an operator you surround it with ÂÂ, or just one
of them for a unary operator.
@a Â+Â @b
@aÂ++
You can't necessarily override their semantics without chaning how Perl
6 interprets the syntax
Woolley Kj <[EMAIL PROTECTED]> wrote:
> Not a biggie, but here is a quick patch for ops.num that should stop
> the warnings about ops 1426 to 1432 not being mentioned there.
It's not really decided, if these opcodes are 'official'. So I'd rather
wait a bit before nailing down ops.num.
> Che
At 10:55 PM +0200 4/20/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 8:10 PM +0200 4/20/04, Leopold Toetsch wrote:
[ unused scalar vtables in aggregates ]
Aren't the relevant vtable slots for aggregates unused anyway?
Only because we've not gotten around to writing the c
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 10:55 PM +0200 4/20/04, Leopold Toetsch wrote:
>>
>>Do you want to reserve these just for implementing perl's scalar context
>>of arrays or hashes, or is there more behind the scene?
> More behind the scenes. (Though that's a good reason too) The proble
On Wed, 21 Apr 2004, Leopold Toetsch wrote:
> PMC-only means, that you'll always have to call e.g. get_integer on the
> PMC, because the PMC might be tied. This limitation isn't really good
> for performance reasons. People might use it most likely in combination
> with natural typed arrays.
Ab
On Tue, 2004-04-20 at 18:06, Leopold Toetsch wrote:
> Aaron Sherman <[EMAIL PROTECTED]> wrote:
This horse is getting a bit ripe, so I'm going to skip most of the
detail. I think we all agree on most of the basics, we just disagree on
what to do with them. That's cool.
I do want to pick a couple o
On Wed, 2004-04-21 at 10:13, Simon Glover wrote:
> Absolutely -- I really, _really_ want to be able to use hyper ops with
> fixed size, floating point arrays, and to have that be as fast as
> possible, as that should make it possible to implement something like
> PDL in the core.
Mistake.
Yo
On Wed, 21 Apr 2004, Aaron Sherman wrote:
> On Wed, 2004-04-21 at 10:13, Simon Glover wrote:
>
> > Absolutely -- I really, _really_ want to be able to use hyper ops with
> > fixed size, floating point arrays, and to have that be as fast as
> > possible, as that should make it possible to imple
At 4:00 PM +0200 4/21/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 10:55 PM +0200 4/20/04, Leopold Toetsch wrote:
Do you want to reserve these just for implementing perl's scalar context
of arrays or hashes, or is there more behind the scene?
More behind the scenes. (Tho
At 11:09 AM +0200 4/21/04, Leopold Toetsch wrote:
I've put in another ICU config patch that adds these 2 options to
Configure.pl:
--icuheaders=(header_dir) Location of headers w/o /unicode
--icushared=(linkeroption)> Full linker command
Cool, thanks. I'll add tinder variants for these on sp
At 11:04 AM -0400 4/21/04, Simon Glover wrote:
On Wed, 21 Apr 2004, Aaron Sherman wrote:
>
You don't want to have to convert to-and-from arrays of PMCs in order to
do those ops, and regardless of what kind of hyper-nifty-mumbo-jumbo you
put into Parrot, that's exactly what you're going to have
[Volunteering snipped]
Keen. KJ, meet Sebastian--Sebastian, KJ.
If you'd both head over to http://auth.perl.org and create accounts,
then pass the info on to Robert he'll get you set up and on your way.
Have at it guys, and thanks.
--
Dan
---
The subject has it all. It's even tested a bit ;)
leo
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> I'm drawing the distinction between an operation
> on the container and an operation on all the
> container's contents here. I think it's the right
> distinction.
Sure. But the prefix C just is the distinction. PerlArray's add,
add_int, bitwise whatever v
Is IntList used outside of some tests?
Can we rename it to IntvalArray?
leo
Aaron Sherman <[EMAIL PROTECTED]> wrote:
> On Tue, 2004-04-20 at 18:06, Leopold Toetsch wrote:
>> Well, yes. Except for the special case, which is nice though:
>>
>> $ time parrot ih.imc #[1]
>> real0m0.370s
>>
>> $ time perl i.pl #[2]
>> real0m5.656s
> That's unrealistic.
No. A re
On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
Here's another tiny patch, to let us fast-fail string_equal if we have
cached hashval's which don't match.
Tested and applied now. I've also adoped JIT/i386 to use string_equal
for C and C string ops. This
At 9:22 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
Here's another tiny patch, to let us fast-fail string_equal if we have
cached hashval's which don't match.
Tested and applied now. I've also adoped JIT/i386 to u
On Wed, 21 Apr 2004, Leopold Toetsch wrote:
> The subject has it all. It's even tested a bit ;)
Since we've already got PMCArray and StringArray, shouldn't we call
this FloatArray rather than FloatvalArray?
(Or alternatively, we could rename the first two to PMCvalArray &
StringvalArray).
On Apr 21, 2004, at 9:05 AM, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
I'm drawing the distinction between an operation
on the container and an operation on all the
container's contents here. I think it's the right
distinction.
Sure. But the prefix C just is the distinction.
Aaron Sherman <[EMAIL PROTECTED]> wrote:
> In fact, Parrot Data Language (if there were such a thing) would likely
> introduce its own runtime-loadable opcode set to operate on a new PMC
> type called a piddle.
It would likely base the piddle object on Parrot's internal datatypes
like IntvalArray
Jeff Clites <[EMAIL PROTECTED]> wrote:
> On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
>> ... a factor ~14 performance increase for the "not equal" case.
> Ah, great!
With an optimized compile (of string.c only) the speed up decreases to
only a factor of 12 :)
> (And the "not equal" case
On Apr 21, 2004, at 10:14 AM, Leopold Toetsch wrote:
The "equal" case was missing one thing: if both strings are COWed
copies,
the compare can be avoided too - it's equally fast then, as "not
equal".
That makes sense, as long as we never optimize substring via a COW copy
with a different strlen
At 11:17 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 10:20 AM, Dan Sugalski wrote:
At 9:22 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
... a factor ~14 performance increase for the "not equal" case.
Ah, great! (And the "not equal" case is
At 10:24 AM -0700 4/21/04, Jeff Clites wrote:
So are you saying, have separate vtable slots for the hyper
operations, but then you only have to fill in the
vtable->hyper_add() slot _if_ you want it to do something other than
applying vtable->add() in a loop (otherwise, do what your
proof-of-con
Allison Randal wrote:
> Okay, languages/perl6 is failing all its tests.
[...]
> Will or Jerome, could you take a minute to explain the direction
> you're taking Parrot::Test? I'll patch P6C::TestCompiler to match the
> new setup, but I want to do an "architecture sanity check" first.
I'm sorry, I'
At 15:15 -0400 4/21/04, Dan Sugalski wrote:
>At 10:24 AM -0700 4/21/04, Jeff Clites wrote:
>>then there wouldn't be any temptation to think of >>+<< as a separate operator.
>
>I think... that'd be bad, generally speaking. (And not just because the math folks
>have tensors and know what to do with
>
> We need to address that, then. If we're doing
> unicode, we damn well need to do it right--å is
> å, regardless of whether it's composed or
> decomposed.
Agreed -- on some level. But If we want to implement Larry's
:u0 (bytes) and :u1 (code points) levels we need to have also
the "more ra
Jonathan Lang wrote:
How would I call attributes? Specifically, what if I'm calling a list
attribute from a scalar object?
my Dog $spot;
my Dog @pack;
$spot->@.legs; # INCORRECT (I hope)
[EMAIL PROTECTED]; # INCORRECT?
@spot.legs;# What if you also have @spot declared?
This que
On Wed, 2004-04-21 at 04:19, Buddha Buck wrote:
> From one C6PAN module:
>
> role Dog {
>has $.collar;
>...
> }
> From a third C6PAN module:
>
> class PoliceDog does Dog does LawEnforcementOfficer { ... }
> role LawEnforcementOfficer {
>method arrest { ... }
>has $.collar;
On Wed, 21 Apr 2004, Brent 'Dax' Royal-Gordon wrote:
> Which actually brings up an interesting question:
>
> class Silly {
> has $.thing=1;
> has @.thing=(2, 3);
> has %.thing=(4 => 5, 6 => 7);
> }
I had assumed that'd be illegal: each of $.thing, @.thing and
On Wed, Apr 21, 2004 at 11:04:02AM +0100, Tim Bunce wrote:
: > Hashes should handle various types of built-in key strings properly
: > by default.
:
: What is "properly" for string?
The way it oughta, whatever that is... I was aiming to set policy
rather than implementation there. :-)
: Is it
On Tue, Apr 20, 2004 at 10:55:51AM -0700, Larry Wall wrote:
The flip side is that, since we won't use C<`> as an operator in Perl
6, you're free to use it to introduce any user-defined operators
you like, including a bare C<`>. All is fair if you predeclare.
Most languages won't even give you that
Matthijs van Duin writes:
> On Tue, Apr 20, 2004 at 10:55:51AM -0700, Larry Wall wrote:
> >The flip side is that, since we won't use C<`> as an operator in Perl
> >6, you're free to use it to introduce any user-defined operators
> >you like, including a bare C<`>. All is fair if you predeclare.
>
On Wed, Apr 21, 2004 at 01:02:15PM -0600, Luke Palmer wrote:
macro infix:\ ($cont, $key)
is parsed(/$?key := (-?\w* | \d+)/)
{
if $key ~~ /^\d+$/ {
"($cont).[$key]";
}
else {
"($cont).«$key»";
}
}
That does all the magic at compile t
On Wed, Apr 21, 2004 at 09:19:12PM +0200, Matthijs van Duin wrote:
> On Wed, Apr 21, 2004 at 01:02:15PM -0600, Luke Palmer wrote:
> > macro infix:\ ($cont, $key)
> > is parsed(/$?key := (-?\w* | \d+)/)
> > {
> > if $key ~~ /^\d+$/ {
> > "($cont).[$key]";
> > }
> >
On Wed, Apr 21, 2004 at 03:37:23PM -0400, John Macdonald wrote:
What about "$x\n"? The backslash already has meaning in strings
I use hash elements far more often outside than inside strings, so I could
live with having to write $x«foo» for interpolated hash elements.
Anyway, you're missing the
(Just a quick post from work. Lost the thread, sorry, so it's not a
f'up.)
Why not use +=, -=, *=, /=, etc.? Arithmetic operators would take just 2
arguments and mutate the first. I always used this technique for
implementing "value-ish" classes in C++:
thing operator +(thing lhs, thing rhs) {
Simon Glover <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Apr 2004, Leopold Toetsch wrote:
>> The subject has it all. It's even tested a bit ;)
> Since we've already got PMCArray and StringArray, shouldn't we call
> this FloatArray rather than FloatvalArray?
Well, a floatArray well be one dealing
At 11:04 PM +0300 4/21/04, Jarkko Hietaniemi wrote:
>
We need to address that, then. If we're doing
unicode, we damn well need to do it right--å is
å, regardless of whether it's composed or
decomposed.
Agreed -- on some level. But If we want to implement Larry's
:u0 (bytes) and :u1 (code poin
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Just to make sure... we're making sure the strings are always
> properly decomposed before comparing, right?
Not in the absence of any rules how to decompose or better when ;) We are
currently still at Larry's level 0 or 1. Hash values and compare
operati
Jeff Clites <[EMAIL PROTECTED]> wrote:
> On Apr 21, 2004, at 9:05 AM, Leopold Toetsch wrote:
> Although, I would think that "@ary += 1" would extend the length of the
> array by one. That is, I can think of logical uses for the
> currently-unimplemented arithmetic ops on PerlArray.
I can think of
Jeff Clites <[EMAIL PROTECTED]> wrote:
> On Apr 21, 2004, at 10:14 AM, Leopold Toetsch wrote:
>> The "equal" case was missing one thing: if both strings are COWed
>> copies,
>> the compare can be avoided too - it's equally fast then, as "not
>> equal".
> That makes sense, as long as we never opti
Jeff Clites <[EMAIL PROTECTED]> wrote:
> On Apr 21, 2004, at 9:05 AM, Leopold Toetsch wrote:
[ just another f'up to separate items ]
> So are you saying, have separate vtable slots for the hyper operations,
> but then you only have to fill in the vtable->hyper_add() slot _if_ you
> want it to do
Jerome Quelin <[EMAIL PROTECTED]> wrote:
> 7. The patch has some, erm, "action at distance" problems, such as the
> pasm files put in /tmp
Is that a side effect or needed?
leo
On Wed, 21 Apr 2004, Leopold Toetsch wrote:
> Our data types are String, PMC, Intval, Floatval. So the naming scheme
> should be ok.
I'm embarrased to say that I'd forgotten that, since I usually think of
them just as ints and floats... Anyway, in that case your naming scheme
is fine.
Apol
At 12:23 AM +0200 4/22/04, Leopold Toetsch wrote:
Jerome Quelin <[EMAIL PROTECTED]> wrote:
7. The patch has some, erm, "action at distance" problems, such as the
pasm files put in /tmp
Is that a side effect or needed?
It's just a side-effect, and we can put the old behavior back, I expect.
--
At 12:22 AM +0200 4/22/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
Just to make sure... we're making sure the strings are always
properly decomposed before comparing, right?
Not in the absence of any rules how to decompose or better when ;) We are
currently still at Larry'
As I sit here and wait for parrot to churn on the output from
compiling a relatively small program, I'm reminded again that imcc's
got some degenerate behaviour when it comes to register coloring and
.locals.
I think it may be a handy thing if someone'd go through and draw up a
set of rules fo
At 4:31 PM -0600 4/21/04, kj wrote:
On 21 Apr 2004, at 15:14, Dan Sugalski wrote:
I've got a Cunning Plan, oddly enough, though the margins of this
e-mail are too small to contain it. As soon as I get it finished
I'm going to pass it onto the list and to a few non-list folks who
I know are deep
Jerome wrote:
>
> I'm sorry, I've been very busy for 2 weeks, and did not have the time to
> continue things regarding this topic. :-(
> I hope to have some more time this week-end, but I'm not even sure...
It happens. :)
> So, very quickly:
> 1. The main goal is to have unified languages tests
At 5:55 PM -0500 4/21/04, Allison Randal wrote:
So, very quickly:
1. The main goal is to have unified languages tests, that is, make
language-tests would get a list of all the test files for all of the
languages, and then run only _one_ harness with all those files. This
would allow for one ni
Dan wrote:
>
> Well... the big problems we were make-related, with some tinder
> issues. Basically if any test suite died really hard the testing
> would stop, and only the last test suite run counted for tinder
> good/bad reporting.
>
> At this point, though, I'm comfortable making it so that
On Wed, Apr 21, 2004 at 11:04:56AM -0400, Simon Glover wrote:
: Why? I was under the impression that in Perl 6 it was going to be
: possible to declare arrays that only contain values of a particular
: type -- I believe the syntax I saw was:
:
:my @array is float;
Just for the record, that
On Wed, Apr 21, 2004 at 01:20:50PM -0400, Dan Sugalski wrote:
: Just to make sure... we're making sure the strings are always
: properly decomposed before comparing, right?
And likewise before hashing.
Larry
On Wed, Apr 21, 2004 at 03:15:37PM -0400, Dan Sugalski wrote:
: The math folks tell me it makes sense. I can come up with a
: half-dozen non-contrived examples, and will if I have to. :-P
I've said this before, and I'll keep repeating it till it sinks in.
The math folks are completely, totally, b
On Wed, Apr 21, 2004 at 02:01:35PM -0600, Doug McNutt wrote:
: I understand that it's not practical extraction and report generation
: and understandably shouldn't be built into perl 6, but the individual
: override capability seems important to me.
I think if you want a mathematical dwim metaoper
On Thu, Apr 22, 2004 at 12:14:27AM +0200, Leopold Toetsch wrote:
: I don't care and mathematicians will like to be able to override e.g.
: »*«.
None of my mail on this subject seems to be getting through to
p6i, and I'm getting frustrated. Perl 6 will *not* be allowing
mathematicians to turn »« i
At 7:02 PM -0500 4/21/04, Allison Randal wrote:
Dan wrote:
Well... the big problems we were make-related, with some tinder
issues. Basically if any test suite died really hard the testing
would stop, and only the last test suite run counted for tinder
good/bad reporting.
At this point, though,
Dan Sugalski wrote:
>
> Applied. (Was there anything besides the /tmp change? That's all that
> was in the attachment)
Calling 'rel2abs' was necessary so Parrot::Test would have the right
path to the test file later when it cd's to the main parrot directory
and calls './parrot'. That's all it ne
On Apr 21, 2004, at 10:20 AM, Dan Sugalski wrote:
At 9:22 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
... a factor ~14 performance increase for the "not equal" case.
Ah, great! (And the "not equal" case is the only one which should be
showing a speed
At 11:17 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 10:20 AM, Dan Sugalski wrote:
At 9:22 AM -0700 4/21/04, Jeff Clites wrote:
On Apr 21, 2004, at 4:05 AM, Leopold Toetsch wrote:
... a factor ~14 performance increase for the "not equal" case.
Ah, great! (And the "not equal" case is
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> I think it may be a handy thing if someone'd go through and draw up a
> set of rules for the use of temps, and things that'll cause the
> register coloring algorithm to go mad. (I'd like to avoid 30 minute
> compile sessions--it's a tad tedious :)
Are you
81 matches
Mail list logo
