Ron Blaschke schrieb:
I'm feeling rather dumb asking this, but F says:
Currently GNU bc is only used for doublechecking Parrot bc.
Now, my question is: Where is "Parrot bc?"
"Parrot bc" is sitting on my local disk, being very disfunctional.
I'll check it in, as soon as it does something
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #36251]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36251 >
There should be no need to pass name if sub is passed, and vice versa.
Passing both
Leopold Toetsch wrote:
Klaas-Jan Stol wrote:
hi,
My question concerns functionality of PMCs and Objects.
while reading the docs about the functionality of classes and
objects, I read that the vtable entries of a class can be overridden
to give the class special behaviour. I'd like to know
On Sun, Jun 12, 2005 at 01:44:43AM -, Will Coleda via RT wrote:
> Any tickets which list "will-parrotodo ..." don't need to have replies
OK.
> And, "chip claimed a ticket???!?"
> * gets the vapors.
--
Chip Salzenberg <[EMAIL PROTECTED]>
Bernhard Schmalhofer wrote:
> Ron Blaschke schrieb:
>>Now, my question is: Where is "Parrot bc?"
> "Parrot bc" is sitting on my local disk, being very disfunctional.
> I'll check it in, as soon as it does something useful.
I see.
> It will Python code generated by ANTLR, and the problem is that
Hi,
I have a class A, that has an object of class B as an attribute.
I've overriden the add() method of class A, and I want to let class B
handle the actual work.
The idea is to make this class B replacable by the user, so he can
override the behaviour of a certain object of A, without disturbi
On Sun, Jun 12, 2005 at 12:52:03AM -0400, William Coleda wrote:
> open currently returns an Undef PMC if it fails to open a file. Should it
> instead return a None? Or, IMO, a Null?
Undef PMC ... or more precisely, any old PMC value that is not
defined() ... seems the most useful return value.
Greetings from the Toetch residence in lovely Herrnbaumgarten,
Austria. The hackathon continues apace. This morning, we've dropped
into communal typing with occasional conversation. I'm focussing on
documentation and cherry picking recent p6i traffic.
And speaking of documentation: At the Austr
On Fri, Jun 10, 2005 at 05:18:19PM -0400, William Coleda wrote:
> Looking through the PGE test examples, it *looks* like subrules are just
> globals.
I'm sure that's not how it'll behave when it's done, though I don't
know PGE well enough yet to suggest how it will work exactly. In the
meantime,
On Wed, Jun 08, 2005 at 10:26:59PM +0100, The Perl 6 Summarizer wrote:
> Loop Improvements
> Oh no! It's the register allocator problems again. One of these days I
> swear I'm going to swot up on this stuff properly, work out whether it's
> really the case that full continuations brea
On Sun, Jun 12, 2005 at 12:43:17PM +0200, Klaas-Jan Stol wrote:
> It seems that at the line, marked with "//***", not the __add method of
> b is called, but that A's __add method is called again.
Well, __add is a multimethod now, not a vtable function. I'm not
surprised your code doesn't work as
On Sun, Jun 12, 2005 at 10:52:37AM +0200, Klaas-Jan Stol wrote:
> I read that when creating a new class, then a new ParrotClass is
> created. (ParrotObject is the PMC that takes care of the
> implementation of a run-time object in Parrot, right?). But, a new
> class can inherit from a built-in PMC
On Wed, Jun 08, 2005 at 10:26:59PM +0100, The Perl 6 Summarizer wrote:
> Missing MMD default functions
> Dan was somewhat bemused to find that the MMD functions' defaults had
> disappeared when he did a sync with subversion. He wondered whether this
> was deliberate. Turns out that it
# New Ticket Created by Will Coleda
# Please include the string: [perl #36255]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36255 >
Neither are p6i archives a good place to keep TODO items. =-)
Chip said that Leo said:
On Wed, Jun 08, 2005 at 12:20:57PM -0700, Larry Wall wrote:
> : I'm not sure how this selection mechanism is meant to be used.
>
> The skip is meant to be applied after filtration. Don't filter out
> things you want to see later, in other words.
Okay, caller done as r4555. Without :label for now
Klaas-Jan Stol wrote:
method __add(left, right)
{
b.__add(left, right); //***
}
.sub __add method
.param pmc self
.param pmc left
.param pmc right
The function signatures of your __add methods are bogus.
Pd = Pl + Pr
is the same as:
Pd = __add(Pl, Pr)
or
On Sun, Jun 12, 2005 at 03:42:14PM +0200, Leopold Toetsch wrote:
> Klaas-Jan Stol wrote:
> >.sub __add method
> > .param pmc self
> > .param pmc left
> > .param pmc right
>
> The function signatures of your __add methods are bogus.
Since __add has defined semantics per Parrot, I think it's
# New Ticket Created by Will Coleda
# Please include the string: [perl #36256]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36256 >
This ticket is a placeholder for the 0.2.2 Release of Parrot.
Please mark any RT issues
# New Ticket Created by Will Coleda
# Please include the string: [perl #36257]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36257 >
This ticket is a placeholder for the 0.2.3 Release of Parrot.
Please mark any RT issues
I've:
- opened tickets for 0.2.2 and 0.2.3,
- moved any child tickets that are children of the tickets for 0.1.3, 0.1.4,
0.2.0 tickets to the 0.2.2 release (nine altogether).
- resolved the old release tickets.
Chip -
Check out https://rt.perl.org/rt3/Ticket/Display.html?id=36256 and obvi
Chip Salzenberg <[EMAIL PROTECTED]> writes:
> On Wed, Jun 08, 2005 at 10:26:59PM +0100, The Perl 6 Summarizer wrote:
>> Loop Improvements
>> Oh no! It's the register allocator problems again. One of these days I
>> swear I'm going to swot up on this stuff properly, work out whether it's
# New Ticket Created by Will Coleda
# Please include the string: [perl #36258]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36258 >
> BTW: a nice to have: include SVN revision of local copy in bug report.
>leo
Jens - is this still an issue?
> [leo - Tue Apr 12 02:44:09 2005]:
>
> Jrieks @ Wmit00 . It . Math . Uni-Wuppertal . De [EMAIL PROTECTED]> wrote:
>
> > wmit01 ~ > perl -v
>
> > This is perl, v5.6.0 built for i586-linux
>
> As it seems to be a perl issue, please check the relevant part of the
On Sun, Jun 12, 2005 at 03:15:22PM +0100, Piers Cawley wrote:
> But if you fallow the calling conventions that looks like:
>
>sub foo {
> $a = 1.
> $c = 10;
> print $c
>
> save_dollar_a_and_only_dollar_a_because_im_going_to_use_it_after_this_function_call
> foo()
>
# New Ticket Created by Will Coleda
# Please include the string: [perl #36259]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36259 >
The generated files/dirs:
src/asmfun.s
chartypes
should be ignored by 'svn st'
With a fairly recent parrot (8308)
oolong:~/research/parrot/languages/m4 coke$ make
cc -g -pipe -fno-common -no-cpp-precomp -I/usr/local/include -pipe -fno-common
-Wno-long-double -I../../include -g -Wall -Wstrict-prototypes
-Wmissing-prototypes -Winline -Wpointer-arith -Wcast-qual -Wcast-al
Chip Salzenberg <[EMAIL PROTECTED]> writes:
> On Sun, Jun 12, 2005 at 03:15:22PM +0100, Piers Cawley wrote:
>> But if you fallow the calling conventions that looks like:
>>
>>sub foo {
>> $a = 1.
>> $c = 10;
>> print $c
>>
>> save_dollar_a_and_only_dollar_a_because_im_goi
I'd like like to note for other readers and the p6i archives that
Piers has failed to grasp the problem, so the solution seems pointless
to him. I'm sorry that's the case, but I've already explained enough.
--
Chip Salzenberg <[EMAIL PROTECTED]>
Verified, still borked in r8328
William Coleda wrote:
With a fairly recent parrot (8308)
oolong:~/research/parrot/languages/m4 coke$ make
cc -g -pipe -fno-common -no-cpp-precomp -I/usr/local/include -pipe
-fno-common -Wno-long-double -I../../include -g -Wall
-Wstrict-prototypes -Wmissing-p
# New Ticket Created by Will Coleda
# Please include the string: [perl #36261]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36261 >
Document how HLL languages can implement their own exception hierarchy, and
perhaps de
At 07:15 AM 6/12/2005, Chip Salzenberg wrote:
Therefore, register allocation must allow for implicit flow of control
from *every* function call to *every* function return ... or, more
precisely, to where *every* continuation is taken, including function
return continuations.
Yes.
But for casu
At 01:16 PM 6/12/2005, MrJoltCola wrote:
At 07:15 AM 6/12/2005, Chip Salzenberg wrote:
1) As far as variable lifetime, the brute-force method would assume
lifetime windows (du-chains) from the first definition of each variable
to the last function call in a basic block. Horrible for optimization.
# New Ticket Created by Will Coleda
# Please include the string: [perl #36262]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36262 >
Anyone looking for some perl6 to do, I need a rule that matches floating-point
numbers
Chip~
On 6/12/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> I'd like like to note for other readers and the p6i archives that
> Piers has failed to grasp the problem, so the solution seems pointless
> to him. I'm sorry that's the case, but I've already explained enough.
This response worries
Matt Fowles <[EMAIL PROTECTED]> writes:
> Chip~
>
> On 6/12/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
>> I'd like like to note for other readers and the p6i archives that
>> Piers has failed to grasp the problem, so the solution seems pointless
>> to him. I'm sorry that's the case, but I've
On 6/12/05, Piers Cawley <[EMAIL PROTECTED]> wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> writes:
>
> > On Sun, Jun 12, 2005 at 03:15:22PM +0100, Piers Cawley wrote:
> >> But if you fallow the calling conventions that looks like:
> >>
> >>sub foo {
> >> $a = 1.
> >> $c = 10;
> >>
On Sun, Jun 12, 2005 at 12:57:56PM +0200, Chip Salzenberg wrote:
> On Fri, Jun 10, 2005 at 05:18:19PM -0400, William Coleda wrote:
> > Looking through the PGE test examples, it *looks* like subrules are just
> > globals.
>
> I'm sure that's not how it'll behave when it's done, though I don't
> kn
On Sun, Jun 12, 2005 at 03:40:55PM -0600, Curtis Rawls wrote:
> I also do not see the wisdom of reducing continuations to just a GOTO.
It really isn't just a goto, at least, not a hardware-CPU-style goto.
By virtue of Parrot's registers living in memory attached to the
activiation record, switchin
On Sun, 2005-06-12 at 07:27 -0700, Will Coleda wrote:
> > BTW: a nice to have: include SVN revision of local copy in bug report.
It looks like it's already in the contents of myconfig at the end of the
bug report; is there more to do here?
-- c
On Sun, Jun 12, 2005 at 12:05:10AM -0400, William Coleda wrote:
> Is it possible to do substitutions with PGE yet? If so, how?
Single (first occurrence) substitutions are possible; simply perform
the match, the match object returns the start/end location
of the item that matched, and then do a su
Chip and I have been having a discussion. I want to write:
sub foo { my $x = 1; return sub { eval $^codestring } }
say foo()("$x");
I claim that that should print 1. Chip claims it should throw a warning about
because of timely destruction. My claim is that a closure should close over the
> Piers Cawley said:
> in other words, some way of declaring that a subroutine wants to hang onto
> every lexical it can see in its lexical stack, not matter what static analysis
> may say.
I'm not arguing with the idea, in general. I just want to point out
that this implies that you're going to h
Piers Cawley wrote:
Chip and I have been having a discussion. I want to write:
sub foo { my $x = 1; return sub { eval $^codestring } }
say foo()("$x");
I claim that that should print 1. Chip claims it should throw a warning about
because of timely destruction. My claim is that a closure
On Sun, Jun 12, 2005 at 11:26:49PM +0100, Piers Cawley wrote:
> Chip and I have been having a discussion. I want to write:
>
> sub foo { my $x = 1; return sub { eval $^codestring } }
> say foo()("$x");
>
> I claim that that should print 1. Chip claims it should throw a warning
> about bec
On Sun, Jun 12, 2005 at 06:22:22PM -0500, Rod Adams wrote:
> Well, you could always do something like:
>
>sub foo { my $x = 1; return sub {my $x := $OUTER::x; eval $^codestring} }
In perl5, that would just be
sub foo { my $x = 1; return sub { $x ; eval $_[0]} }
--
You live and learn (a
Probably not. I was merely trying to save an RFE I saw in one of leo's mails.
If it looks like it's there, feel free to close the ticket.
chromatic wrote:
On Sun, 2005-06-12 at 07:27 -0700, Will Coleda wrote:
BTW: a nice to have: include SVN revision of local copy in bug report.
It looks
I just set up a new list for pirate, a python
compiler for parrot.
Quite a bit of work has been done on pirate since I
last updated the website back in 2003, mostly by
Sam Ruby of http://intertwingly.net/
Sam is giving a python-on-parrot presentation at
OSCON on August 4, so I'd like to
On 6/12/05, Dave Mitchell <[EMAIL PROTECTED]> wrote:
> You may be using slow evals, but other fast code may not be. Should the
> closure in
>
> sub foo { my $x = 1; return sub { 1 } }
>
> also capture the current instance of $x? You are basically condeming any
> code that creates any closure,
On 6/12/05, Curtis Rawls <[EMAIL PROTECTED]> wrote:
>
> [snip]
> It might also be helpful to take a look at other systems that also
> implement continuations:
> -Stackless Python (http://www.stackless.com/spcpaper.htm)
> -Standard ML (http://www.smlnj.org/doc/features.html)
> -Formalizing Implemen
On Sun, Jun 12, 2005 at 11:26:49PM +0100, Piers Cawley wrote:
> sub foo { my $x = 1; return sub { eval $^codestring } }
> say foo()("$x");
I'm pretty sure you meant single-quoted, and you perhaps might maybe
need a dot there:
sub foo { my $x = 1; return sub { eval $^codestring } }
On Mon, Jun 13, 2005 at 12:57:32AM +0200, Chip Salzenberg wrote:
> On Sun, Jun 12, 2005 at 11:26:49PM +0100, Piers Cawley wrote:
> > sub foo { my $x = 1; return sub { eval $^codestring } }
> > say foo()("$x");
>
> I'm pretty sure you meant single-quoted, and you perhaps might maybe
> need
51 matches
Mail list logo
