On Nov 29, 2005, at 1:45, jerry gay wrote:
the parrot directory structure is large and a bit disorganized.
let me give you some examples:
* build_tools/, util/, and tools/*/ each contain utility perl
scripts. these should be grouped together under tools/, which
already contains subdirectori
jerry gay wrote:
+---t
| +---compilers
| | +---imcc # moved from imcc/t/
| | |
This doesn't really work for me. imcc/t* used to test some general
parsing features, code generation and register allocation. Therefore it
should run early in the tests.
What about
Leopold Toetsch wrote:
The whole scratchpad is doomed and will be scratched RSN (see pdd20
instead).
Committed as r10240.
All tests are passing on linux/x86 and linux-64/amd64.
Please make realclean ...
leo
> On 2005-11-02, Luke Closs <[EMAIL PROTECTED]> wrote:
> >
> > Also, yesterday Test::WWW::Selenium was uploaded to CPAN, so Selenium
> > can now be driven by perl!
>
> Test::WWW::Selenium seems interesting, but I could use an example it
> would be useful to use, versus the standard techniques.
I
Chip Salzenberg wrote:
On Fri, Nov 25, 2005 at 11:45:40PM +0100, Leopold Toetsch wrote:
catch_label:
get_results "(...)", Pexcept, Smessage, ... # whatever
This part is now implemented (r10241). (Funnily it did work immediately :)
Currently exactly these 2 arguments (exception, messag
On Nov 29, 2005, at 8:38 AM, Leopold Toetsch wrote:
Chip Salzenberg wrote:
On Fri, Nov 25, 2005 at 11:45:40PM +0100, Leopold Toetsch wrote:
catch_label:
get_results "(...)", Pexcept, Smessage, ... # whatever
This part is now implemented (r10241). (Funnily it did work
immediately :
On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> jerry gay wrote:
>
> > +---t
> > | +---compilers
> > | | +---imcc # moved from imcc/t/
> > | | |
>
> This doesn't really work for me. imcc/t* used to test some general
> parsing features, code generation and reg
Will Coleda wrote:
On Nov 29, 2005, at 8:38 AM, Leopold Toetsch wrote:
handler:
get_results "(0,0)", P0, S0
Currently, partcl stores extra information in P5[9] - Would it be
available as P0[9] in your example? (If so, is the message still
available as P0[0] ?
Sure. Nothing has
Leopold Toetsch wrote:
Syntactic sugar, ...
Done - r10243. Again exactly 2 arguments are supported for now:
handler:
.local pmc e
.local string mess
.get_results (e, mess)
Variable decls after the handler label aren't instructions and therefore ok.
See also t/pm
On 11/29/05, jerry gay <[EMAIL PROTECTED]> wrote:
> On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> > This doesn't really work for me. imcc/t* used to test some general
> > parsing features, code generation and register allocation. Therefore it
> > should run early in the tests.
> >
> you
On 11/28/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 28, 2005 at 04:45:33PM -0800, jerry gay wrote:
> > i propose reorganizing the tree to improve clarity and cohesion.
>
> Reorganization would be good at this point, but should be undertaken
> cautiously so as to minimize unpleasan
On 11/28/05, Matt Diephouse <[EMAIL PROTECTED]> wrote:
> I'd really like to see imcc/docs/ get moved to docs/imcc/ while we're
> moving things around. I know that some people consider imcc to be
> rather separate from parrot, but as a compiler writer, I see it as a
> core feature. I always seem to
On 11/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> On Nov 29, 2005, at 1:45, jerry gay wrote:
> > the parrot directory structure is large and a bit disorganized.
> > let me give you some examples:
> > * build_tools/, util/, and tools/*/ each contain utility perl
> > scripts. these should b
Hi all!
These are some extra test files that I added to Test::Run, and possibly could
be integrated into Test::Harness after some modification:
t/output.t:
#!/usr/bin/perl -w
BEGIN {
if( $ENV{PERL_CORE} ) {
chdir 't';
@INC = ('../lib', 'lib');
}
els
On Nov 29, 2005, at 8:38 AM, Leopold Toetsch wrote:
Chip Salzenberg wrote:
On Fri, Nov 25, 2005 at 11:45:40PM +0100, Leopold Toetsch wrote:
catch_label:
get_results "(...)", Pexcept, Smessage, ... # whatever
This part is now implemented (r10241). (Funnily it did work
immediately :
On Tue, 2005-11-29 at 13:24 +0100, Leopold Toetsch wrote:
> All tests are passing on linux/x86 and linux-64/amd64.
>
> Please make realclean ...
All tests pass on Linux/PPC. There's one bonus in PGE's Unicode, but
that's a happy notice.
-- c
On Tue, Nov 29, 2005 at 04:26:09PM +0100, Leopold Toetsch wrote:
> Coke:
> >If so, why do we specify S0 here?)
>
> Just for convenience.
I appreciate the convenience argument, but given the ease of keyed
access, $P0[0] is pretty darned convenient already. And someday we
may want to pass things t
Consider:
P0 = P1
P0 = S1
P0 = I1
P0 = N1
o/~ One of these things is not like the others
One of these things just doesn't belong o/~
And if I have to read:
P0 = new .Integer
P0 = 1
one more time... *sigh*
Therefore, I propose requiring people to spell aliasing as ':
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
>P0 := P1 # aliasing: P0 and P1 point to same PMC
>P0 := opcode # aliasing: P0 points to PMC returned by opcode
>P0 = ... # assignment: modifies P0, NO MATTER WHAT '...' IS
>
>S0 := S1 # aliasing: S0 and S1 point to sa
On Tue, Nov 29, 2005 at 12:08:01PM -0800, Chip Salzenberg wrote:
> Therefore, I propose requiring people to spell aliasing as ':='. This will
> affect all code generated to use P and S registers. It should be an easy fix
> (albeit an extensive one). And if we don't do it now, it'll just get hard
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> And if I have to read:
>
>P0 = new .Integer
>P0 = 1
>
> one more time... *sigh*
>
> Therefore, I propose requiring people to spell aliasing as ':='. This will
> affect all code generated to use P and S registers. It should be an easy fix
> (a
On Tue, Nov 29, 2005 at 12:14:24PM -0800, Brent 'Dax' Royal-Gordon wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> >P0 := P1 # aliasing: P0 and P1 point to same PMC
> >P0 := opcode # aliasing: P0 points to PMC returned by opcode
> >P0 = ... # assignment: modifies P0
On Tue, Nov 29, 2005 at 02:18:17PM -0600, Patrick R. Michaud wrote:
> Personally I haven't had much trouble with '=' and I don't think
> I ever use ':='. Perhaps I've just trained myself to the current
> implementation, but I like that the shorter '=' does what I tend
> to want/expect and I write
On Tue, Nov 29, 2005 at 02:18:17PM -0600, Patrick R. Michaud wrote:
> On Tue, Nov 29, 2005 at 12:08:01PM -0800, Chip Salzenberg wrote:
> >P0 := P1 # aliasing: P0 and P1 point to same PMC
> >P0 := opcode # aliasing: P0 points to PMC returned by opcode
> >P0 = ... # assignm
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 29, 2005 at 12:14:24PM -0800, Brent 'Dax' Royal-Gordon wrote:
> > I'm not sure about the last two (in a lot of ways, they're more like
> > := than = ),
>
> I don't see that.
Well, for one thing, my way would mean that `set` is always `:=`.
On Tue, Nov 29, 2005 at 03:25:13PM -0500, Matt Diephouse wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> > Therefore, I propose requiring people to spell aliasing as ':='.
>
> "And the Lord did grin. And the people did feast upon the lambs and
> sloths, and carp and anchovies, and orangutans
On Tue, Nov 29, 2005 at 12:36:03PM -0800, Chip Salzenberg wrote:
> On Tue, Nov 29, 2005 at 02:18:17PM -0600, Patrick R. Michaud wrote:
> > P0 = P1[S1]# supported?
>
> Yes, it means to fetch a PMC and make P0 an alias to it. Perl 6
> equivalent should be, more or less:
>
> $a := $arra
On Tue, Nov 29, 2005 at 12:36:03PM -0800, Chip Salzenberg wrote:
> On Tue, Nov 29, 2005 at 02:18:17PM -0600, Patrick R. Michaud wrote:
> > Second comment: how about access to keyed items -- does this mean:
> >
> > P0 := P1[S1] # alias
> > S0 = P1[S1]# assignment
> > I0 = P1[S1]
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Tue, 29 Nov 2005 12:27:03 -0800
On Tue, Nov 29, 2005 at 12:14:24PM -0800, Brent 'Dax' Royal-Gordon wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> >P0 := P1 # aliasing: P0 and P1 point to same PMC
> >P0 := opcod
On Tue, Nov 29, 2005 at 12:38:55PM -0800, Brent 'Dax' Royal-Gordon wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> > On Tue, Nov 29, 2005 at 12:14:24PM -0800, Brent 'Dax' Royal-Gordon wrote:
> > > I'm not sure about the last two (in a lot of ways, they're more like
> > > := than = ),
> >
> >
On Tue, Nov 29, 2005 at 03:55:22PM -0500, Bob Rogers wrote:
> So "aliasing" copies the pointer (i.e. the object itself), and
> "assignment" copies the value?
Right. Note, however, that you have to *have* a pointer for "copying
the pointer" to be meaningful. Thus, since I and N registers are not
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> On Tue, Nov 29, 2005 at 03:25:13PM -0500, Matt Diephouse wrote:
> > Or, perhaps more accurately, `P1 := ...\n assign P0, P1`?
>
> No, PIR doesn't do that kind of thing (allocating P registers) behind
> your back. If a sequence needs a second P register,
On Tue, Nov 29, 2005 at 04:27:28PM -0500, Matt Diephouse wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> > On Tue, Nov 29, 2005 at 03:25:13PM -0500, Matt Diephouse wrote:
> > > Or, perhaps more accurately, `P1 := ...\n assign P0, P1`?
> >
> > No, PIR doesn't do that kind of thing (allocating
On Nov 25, 2005, at 23:45, Leopold Toetsch wrote:
The last (and never done correctly) relict of old calling
conventions...
... is gone now. Please consult docs/compiler_faq.pod or this thread
for using get_results instead.
From r10257
Exception handler code: P5 is gone
The compat code ca
On Nov 29, 2005, at 21:36, Chip Salzenberg wrote:
I'm planning a flag day sometime in December. I'm also planning to
create a simple "handles most cases" translator.
That's all ok with me, but not without an automatic translator, that
"handles 99.99% cases". As the current syntax is clear,
On Tue, Nov 29, 2005 at 11:13:05PM +0100, Leopold Toetsch wrote:
> On Nov 29, 2005, at 21:36, Chip Salzenberg wrote:
> >I'm planning a flag day sometime in December. I'm also planning to
> >create a simple "handles most cases" translator.
>
> That's all ok with me, but not without an automatic tr
Chip~
On 11/29/05, Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> Consider:
>
>P0 = P1
>P0 = S1
>P0 = I1
>P0 = N1
>
> o/~ One of these things is not like the others
> One of these things just doesn't belong o/~
>
> And if I have to read:
>
>P0 = new .Integer
>P0 = 1
>
# New Ticket Created by jerry gay
# Please include the string: [perl #37787]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37787 >
parent ticket, used to track overall progress. see
http://groups.google.com/group/perl.per
# New Ticket Created by jerry gay
# Please include the string: [perl #37789]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37789 >
this will likely require configure, makefile, build, and documentation
modifications. rela
# New Ticket Created by jerry gay
# Please include the string: [perl #37788]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37788 >
this requires makefile changes, and a website generation code update:
(see will at coleda
# New Ticket Created by jerry gay
# Please include the string: [perl #37791]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37791 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37800]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37800 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37793]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37793 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37794]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37794 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37790]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37790 >
this will likely require configure, makefile, build, and documentation
modifications. rela
# New Ticket Created by jerry gay
# Please include the string: [perl #37792]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37792 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37802]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37802 >
this will likely require configure, makefile, and documentation
modifications. this should
On Tue, 2005-11-29 at 12:08 -0800, Chip Salzenberg wrote:
> Therefore, I propose requiring people to spell aliasing as ':='.
Is some different symbol possible, to avoid confusing people who use
Algol-like languages where ":=" means assignment (Amber, Ada, Eiffel,
Delphi...)?
How about:
"=>"
> > >If so, why do we specify S0 here?)
> >
> > Just for convenience.
In most places, I don't use the string. I'd rather just get the PMC.
Regards,
Roger Browne
# New Ticket Created by jerry gay
# Please include the string: [perl #37799]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37799 >
this will likely require configure, makefile, build, and documentation
modifications. this
Check:
http://www.flickr.com/photos/[EMAIL PROTECTED]/68430623/
This was done by using Test::Run::CmdLine's runprove (a yet-incomplete
equivalent of Test::Harness' prove) and the
Test::Run::CmdLine::Drivers::ColorSummary driver that is in fact a sub-class
of Test::Run, my fork of Test::Harness
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Tue, 29 Nov 2005 13:07:22 -0800
On Tue, Nov 29, 2005 at 03:55:22PM -0500, Bob Rogers wrote:
> So "aliasing" copies the pointer (i.e. the object itself), and
> "assignment" copies the value?
Right. Note, however, that you have to *
# New Ticket Created by jerry gay
# Please include the string: [perl #37798]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37798 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37801]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37801 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37795]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37795 >
this will likely require configure, makefile, build, and documentation
modifications. this
On Tue, Nov 29, 2005 at 05:17:25PM -0500, Matt Fowles wrote:
> I very much like it. I think I may have suggested something like it
> earlier (although I might have only thought it).
It's entirely possible. Great minds think alike ... and us too,
apparently. :-)
> "Computer Science is merely th
On Tue, Nov 29, 2005 at 10:45:12PM +, Roger Browne wrote:
> On Tue, 2005-11-29 at 12:08 -0800, Chip Salzenberg wrote:
> > Therefore, I propose requiring people to spell aliasing as ':='.
>
> Is some different symbol possible, to avoid confusing people who use
> Algol-like languages where ":="
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Tuesday 29 November 2005 23:28, Shlomi Fish wrote:
> Check:
>
> http://www.flickr.com/photos/[EMAIL PROTECTED]/68430623/
>
> This was done by using Test::Run::CmdLine's runprove (a yet-incomplete
> equivalent of Test::Harness' prove) and the
> Test::Run
# New Ticket Created by jerry gay
# Please include the string: [perl #37796]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37796 >
this will likely require configure, makefile, build, and documentation
modifications. this
# New Ticket Created by jerry gay
# Please include the string: [perl #37797]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37797 >
this will likely require configure, makefile, build, and documentation
modifications. this
On Tue, Nov 29, 2005 at 05:51:42PM -0500, Bob Rogers wrote:
>I think of PMCs as being objects, not containers for something else,
> and ":=" as meaning "copy the object" (which is synonymous with "copy
> the reference to the object") and "=" as "copy the contents." Under
> this interpretation,
Hi,
I seem to be touching a bug related to writing compiled code.
pir_comp = compreg "PIR"
pbc_out = pir_comp(gen_pir)
fh = open output
print fh, pbc_out
close fh
On the print line, I get this error:-
directory_pack segment 'BYTECODE_EVAL_1' used size 158 but reported 160
This used to work -
I've reviewed pdd03 and brought it back from pdds/clip. Mostly it's
the same as before, albeit with clarifications and a few flag bits
renamed to match PIR. I have made a couple actual changes, though.
On the small side, there's a barest hint of named parameters.
Most importantly, I've proposed
On Nov 29, 2005, at 15:08, Chip Salzenberg wrote:
Comments? Fresh or rotten vegetables?
My objections:
Consider:
P0 = P1
P0 = S1
P0 = I1
P0 = N1
o/~ One of these things is not like the others
One of these things just doesn't belong o/~
And if I have to read:
P0 =
Hi Tels! (and all)
On Wednesday 30 November 2005 00:49, Tels wrote:
> Moin,
>
> On Tuesday 29 November 2005 23:28, Shlomi Fish wrote:
> > Check:
> >
> > http://www.flickr.com/photos/[EMAIL PROTECTED]/68430623/
> >
> > This was done by using Test::Run::CmdLine's runprove (a yet-incomplete
> > equiv
65 matches
Mail list logo
