Jerome Quelin wrote:
eq S0, , FLOW_GO_WEST
[ branch not taken ]
And while I'm talking about strange things... Due to the fact that Parrot
does not branch to the correct label,
As strings are involved, could you insert:
sweepoff
collectoff
as the very first
On Fri, 4 Oct 2002, Michael Lazzaro wrote:
: Date: Fri, 4 Oct 2002 16:40:04 -0700
: From: Michael Lazzaro [EMAIL PROTECTED]
: To: [EMAIL PROTECTED]
: Subject: Draft Proposal: Declaring Classwide Attributes
:
: (Disclaimer: My purpose in proposing this is not to recommend it, but
: to document
in
http://archive.develooper.com/perl6-language%40perl.org/msg11440.html
Larry Wall wrote:
I'm wondering whether the single ones could indicate parallel streams.
We had the difficulty of specifying whether the Cfor loop should
terminate on the shorter or the longer stream. We could say that |
in
http://archive.develooper.com/perl6-language%40perl.org/msg11451.html
Larry Wall wrote:
for cases ^| newcases - $x is rw | $y {...}
do I understand correctly that what happens is (more or less) --
any($a,$b) := any($x,$y)
?
arcadi
Date: Fri, 11 Oct 2002 12:16:00 -0700 (PDT)
From: Larry Wall [EMAIL PROTECTED]
I'm wondering whether the single ones could indicate parallel streams.
We had the difficulty of specifying whether the Cfor loop should
terminate on the shorter or the longer stream. We could say that |
On Fri, 4 Oct 2002, Michael Lazzaro wrote:
: Thanks, if it's looking like lvalues are really out I'll edit that draft
: to take out the lvalue stuff and do it the other way.
No, lvalue methods are definitely in, and pretty much always have been.
(There will be no problem with post-processing the
Jerome Quelin wrote:
My goal is to provide a Befunge interpreter that just does the right thing
out of the box - that is, that does not need to patch Parrot in order to
function.
Arrays (and all classes) are currently reorganized. The mentioned patch
is a current hack, to get your
Luke Palmer writes:
Some of my students want to go:
if ($x == 1 || 2) { ... }
Now they can:
if $x == 1 | 2 { ... }
I like that a lot. (Some of my students also want to do that.)
You can write an equivalent thing in Icon:
if x = (0 | 1)
though (if memory serves) the
On Sat, 12 Oct 2002, Me wrote:
: We also need a signifier for class methods (assuming
: a distinction is made).
:
: Perhaps one could use an initial cap to indicate a class
: attribute/method:
:
: class foo {
: my $bar;# my is not used for attributes
: our $baz;# neither
On Sat, 5 Oct 2002, John Williams wrote:
: I think everyone agrees that some sort of simple accessor syntax will be
: included (instead of the getX/setX hack). But will accessors _look_ like
: attributes or methods?
:
: # look like methods
: object.foo($value);
:
: # look like
Larry Wall [EMAIL PROTECTED] writes:
On Sat, 12 Oct 2002, Me wrote:
: We also need a signifier for class methods (assuming
: a distinction is made).
:
: Perhaps one could use an initial cap to indicate a class
: attribute/method:
:
: class foo {
: my $bar;# my is not used
On Sat, 12 Oct 2002, Chris Dutton wrote:
: On Saturday, October 12, 2002, at 01:10 PM, Luke Palmer wrote:
:
: Date: Sat, 12 Oct 2002 08:43:46 -0700 (PDT)
: From: Larry Wall [EMAIL PROTECTED]
:
: If we use | and as sugar for any() and all(), then their precedence
: should probably be the
Trey Harris wrote:
In a message dated Sun, 13 Oct 2002, Piers Cawley writes:
I like that idea:
class SomeClass {
method class_method ( Class $class: ... ) { ... }
method instance_method ( SomeClass $self : ... ) { ... }
method dont_care_method (
Tom Hughes wrote:
In message [EMAIL PROTECTED]
Leopold Toetsch (via RT) [EMAIL PROTECTED] wrote:
It's probably best to do whatever C99 does, which I think is the same
as what glibc does, namely to return the amount of space that would be
needed to avoid truncation if the result
Jerome Quelin wrote:
Hi there,
I just discovered that:
a) my befunge interpreter is broken (would you stop beaking it please? :o))
b) push and pop operations are now supported by lists
c) there's a pmc for handling list of integers: intlist
So, what else can I do? Catching
On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote:
Perhaps this is a known issue...
Most parrot programs seem to crash on x86 when the latest CVS parrot
is compiled with -O2 or -g -O2 and when JIT is enabled.
The programs appear to run to completion and only crash prior to
On Saturday 12 October 2002 18:26, Brent Dax wrote:
# So, what else can I do? Catching exceptions (is that possible
# with Parrot)?
Not just yet. The ideas for exceptions are still bouncing around in the
caverns of Dan's brain. :^)
So, what am I suppose to do? Is there a way to get the
On Sat, Oct 12, 2002 at 07:29:04PM +0200, Jerome Quelin wrote:
FYI, I just rsync'ed this afternoon (12/10/2002 14:52 GMT) my Parrot, and did
the traditionnal: perl Configure.pl ; make; make test
and yes, all the tests went ok...
I'll look into it, but could you try doing a make clean first?
--Brent Dax [EMAIL PROTECTED]
@roles=map {Parrot $_} qw(embedding regexen Configure)
Wire telegraph is a kind of a very, very long cat. You pull his tail in
New York and his head is meowing in Los Angeles. And radio operates
exactly the same way. The only difference is that there is no cat.
On Fri, Oct 11, 2002 at 04:08:27PM +, Simon Glover wrote:
# New Ticket Created by Simon Glover
# Please include the string: [perl #17865]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17865
One of the
Jerome Quelin:
# On Saturday 12 October 2002 18:26, Brent Dax wrote:
# # So, what else can I do? Catching exceptions (is that
# possible # with
# Parrot)? Not just yet. The ideas for exceptions are still bouncing
# around in the caverns of Dan's brain. :^)
#
# So, what am I suppose to
On Saturday 12 October 2002 17:56, Leopold Toetsch wrote:
So, what else can I do? Catching exceptions (is that possible with
Parrot)?
Please have a look at list - not a PMC currently but can/does simulate
intlist now for testing. just compile/link list instead of intlist.
list_pop(...)
On Fri, Oct 11, 2002 at 05:02:02PM -0700, Larry Wall wrote:
On Fri, 11 Oct 2002, Michael Lazzaro wrote:
: On Friday, October 11, 2002, at 04:11 PM, Larry Wall wrote:
:has Nose $.snout;
:has Ear @.ears is cut(long);
:has Leg @.legs;
:has Tail $.tail is cut(short);
:
:
On Sat, Oct 12, 2002 at 04:53:57PM +0200, Jerome Quelin wrote:
But I have a problem. When popping a value from an empty list, I get a No
entries on list! exception. Instead, I want to get a zero. I can add
something like:
CHECK_EMPTY:
set I0, P2
eq I0, 0, PUSH_ZERO
ret
On Fri, 11 Oct 2002, Trey Harris wrote:
: When you say subclass, do you mean below the current class in the
: naming heirarchy, i.e.
:
: class BTree;
: our class Node {...}
:
: would create BTree::Node? Or do you really mean *subclass*, i.e., our
: class causes Node to inherit from BTree?
In a message dated Sun, 13 Oct 2002, Piers Cawley writes:
I like that idea:
class SomeClass {
method class_method ( Class $class: ... ) { ... }
method instance_method ( SomeClass $self : ... ) { ... }
method dont_care_method ( $self : ... ) { ... }
}
On Sat, 12 Oct 2002, Larry Wall wrote:
: The precedence is screwed up though. It'd have to be
:
: use Acme[ (1;17..) | (2;0..) ];
Or maybe this:
use Acme[1;17..] |
Acme[2;0..];
That doesn't, of course, express any preference for one version over another,
since | logically
On Fri, 11 Oct 2002, Luke Palmer wrote:
: I now realize I'm a little fuzzy on the yada-yada-yada operator. What
: exactly is it... or what does it do? Is it a statement, an
: expression?
It's a term.
: Could you say things like:
:
: foo(...);
Yes.
: (Admittedly I have no idea what that
Date: Sat, 12 Oct 2002 08:43:46 -0700 (PDT)
From: Larry Wall [EMAIL PROTECTED]
If we use | and as sugar for any() and all(), then their precedence
should probably be the same as || and .
Should they? I had in mind something just above comparisons. That
way:
if $x == 3 || $y ==
I've looked before for discussion of the rationale behind
introducing attr/has and failed to find it. I noticed you
mention Zurich, so perhaps this decision followed from
discussion in living color (as against b+w).
Anyhow, what was deemed wrong with using my/our?
And...
class Zap {
my
Nothing the matter with our for class attributes since they're
already stored in the package if we follow Perl 5's lead. But using
my for instance attributes is problematic if we allow a class to
be reopened:
class Blurfl {
my $.foo;
}
...
class Blurfl is continued {
On Sat, 12 Oct 2002, Luke Palmer wrote:
: Date: Sat, 12 Oct 2002 08:43:46 -0700 (PDT)
: From: Larry Wall [EMAIL PROTECTED]
:
: If we use | and as sugar for any() and all(), then their precedence
: should probably be the same as || and .
:
: Should they? I had in mind something just above
On Thu, 10 Oct 2002, Larry Wall wrote:
: Anyway, I don't see offhand why composition can't simply be done with
: attributes as it is in C++, especially since attributes manifest as
: methods outside the class. I don't think $car.cd.eject() is all that
: horrible to contemplate.
By the way, ever
On Friday, October 11, 2002, at 04:11 PM, Larry Wall wrote:
has Nose $.snout;
has Ear .ears is cut(long);
has Leg .legs;
has Tail $.tail is cut(short);
method Wag () {...}
}
What's the rationale again for the dot in $.snout? Does it imply that
it
On Sat, 12 Oct 2002 08:43:46 -0700, Larry Wall wrote:
On Sat, 12 Oct 2002, Graham Barr wrote:
: Or even something like
:
: use Acme[1.0];
Hmm. Looks kinda like a subscript, which could be sliced to give an
acceptable version range:
use Acme[1;0..];
Might it be possible to say
On Fri, 11 Oct 2002, Dan Sugalski wrote:
: I think that, for me at least, it'll be close enough to C to be
: really confusing. (I already have the problem of leaving parens off
: of my function calls when I write XS code...) There's a certain
: appeal to not having to swap in
On Sunday 13 October 2002 12:11, Leopold Toetsch wrote:
Jerome Quelin wrote:
eq S0, , FLOW_GO_WEST
[ branch not taken ]
And while I'm talking about strange things... Due to the fact that Parrot
does not branch to the correct label,
As strings are involved, could you insert:
From my point of view - it isn't.
As I said in an earlier post, my Befunge interpreter is broken. It was doing
well not so long ago. Anyway, since I wanted to add intlists and push/pop, I
made some modifications. But I can't test them, since Parrot seems to be
badly broken...
At first, I
On Sunday 13 October 2002 12:16, Steve Fink wrote:
On Sat, Oct 12, 2002 at 07:29:04PM +0200, Jerome Quelin wrote:
FYI, I just rsync'ed this afternoon (12/10/2002 14:52 GMT) my Parrot, and
did the traditionnal: perl Configure.pl ; make; make test
and yes, all the tests went ok...
I'll look
On Sat, 12 Oct 2002, Me wrote:
: I've looked before for discussion of the rationale behind
: introducing attr/has and failed to find it. I noticed you
: mention Zurich, so perhaps this decision followed from
: discussion in living color (as against b+w).
:
: Anyhow, what was deemed wrong with
On Fri, 11 Oct 2002, Larry Wall wrote:
: You can certainly drop it within the methods,
: since there's also the accessor methods.
But I should point out that there's a semantic difference between
$.foo and .foo, in that $.foo is guaranteed to get my copy of the
attribute, while .foo might just
On Sat, 12 Oct 2002, Larry Wall wrote:
On Sat, 5 Oct 2002, John Williams wrote:
: Personally, I hope they look like attributes.
They will, outside the class anyway. Inside it's $.foo.
: But if they do, the perl5
: lvalue subs are not the way to do it. Why? Because an lvalue sub returns
On Sat, 12 Oct 2002, Dan Kogai wrote:
: Objection, your honor.
:
: perl5 ($x $y) might be uncommon enough to justify this. But how
: about = vs. =, |= vs. ||= ? Those are both used very often so by
: saving one symbol we lose consistency.
Ouch. You're right. That's a bit of a problem for
On Saturday, October 12, 2002, at 01:10 PM, Luke Palmer wrote:
Date: Sat, 12 Oct 2002 08:43:46 -0700 (PDT)
From: Larry Wall [EMAIL PROTECTED]
If we use | and as sugar for any() and all(), then their precedence
should probably be the same as || and .
Should they? I had in mind something
On Sat, 12 Oct 2002, Graham Barr wrote:
: Or even something like
:
: use Acme[1.0];
Hmm. Looks kinda like a subscript, which could be sliced to give an
acceptable version range:
use Acme[1;0..];
Except slices aren't powerful enough to say what you really want to say:
use
# New Ticket Created by Simon Glover
# Please include the string: [perl #17896]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17896
This patch:
i) Adds several new tests for PerlHash, specifically:
-
On Sun, Oct 13, 2002 at 03:06:48AM -0700, Steve Fink wrote:
On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote:
Perhaps this is a known issue...
Most parrot programs seem to crash on x86 when the latest CVS parrot
is compiled with -O2 or -g -O2 and when JIT is enabled.
The
# New Ticket Created by Simon Glover
# Please include the string: [perl #17899]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17899
This patch:
1) Fixes some minor nits in the assembler documentation (mostly
# New Ticket Created by Simon Glover
# Please include the string: [perl #17901]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17901
Patch below adds tests for the eq, ne, lt, le, gt, ge neg ops for
PerlInts
# New Ticket Created by Simon Glover
# Please include the string: [perl #17903]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17903
Here's a brief test for the PMC, PMC, PMC form of the sprintf op;
as an added
On Sun, Oct 13, 2002 at 11:08:02PM +0100, Nicholas Clark wrote:
On Sun, Oct 13, 2002 at 03:06:48AM -0700, Steve Fink wrote:
On Fri, Oct 11, 2002 at 05:05:56PM -0700, Joe Wilson wrote:
Perhaps this is a known issue...
Most parrot programs seem to crash on x86 when the latest CVS
On Sun, 13 Oct 2002, Steve Fink wrote:
[Discussion snipped]
Yes, I get this also. I was trying to figure out how to properly use
TODO or SKIP or something to suppress this, but none of them worked
quite right -- it would say that the failed test was a TODO, but it
still counted it as a
# New Ticket Created by chromatic
# Please include the string: [perl #17907]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17907
I've been browsing the docs, and took the time to do a bit of copyediting.
There's
I've just tried to write PASM like:
new P0, .IntList
new P1, .PerlInt
set P1, 20
set P0[0], P1
...
end
only to have it fail with the message:
'Subscript on something that's not an aggregate!'
Is this a bug or a feature?
Simon
Simon Glover:
# On Sun, 13 Oct 2002, Steve Fink wrote:
# Your problem was probably forgetting to use Test::More
# (which defines skip). In any case, the enclosed patch should
# do the trick.
#
# +SKIP: { skip(Doesn't work with JIT enabled, 1);
# output_like('CODE', 'OUTPUT', restart trace);
On Sun, Oct 13, 2002 at 11:43:23PM -0400, Simon Glover wrote:
I've just tried to write PASM like:
new P0, .IntList
new P1, .PerlInt
set P1, 20
set P0[0], P1
...
end
only to have it fail with the message:
'Subscript on something that's not an
56 matches
Mail list logo
