Patrick R. Michaud wrote:
Of course, in the previous object model I think there was only
one place to look, and find_method did the searching.
In the previous model, there was no distinction between subroutines and
methods. Any method could be called as a subroutine, and any subroutine
coul
On Wed Dec 19 12:15:39 2007, doughera wrote:
> This patch updates PLATFORMS for my Solaris 8 system, based on
> parrot-0.5.1.
>
> --- parrot-0.5.1/PLATFORMSWed Dec 19 13:35:14 2007
> +++ parrot-andy/PLATFORMS Wed Dec 19 15:10:11 2007
> @@ -31,7 +31,8 @@
> linux-x86_64-gcc4.1.0 4
On Saturday 01 December 2007 14:29:48 Will Coleda wrote:
> from DEPRECATED.pod
>
> =item B
>
> There are several variants of some of the above ops; all are deprecated,
> and are replaced by the ops {set,get}_[hll,root]_global. See also
> http://www.parrotcode.org/docs/ops/var.html.
I poked at thi
On Wed, Dec 19, 2007 at 10:57:27PM -0600, Patrick R. Michaud wrote:
> On Wed, Dec 19, 2007 at 11:15:46PM +0100, Mehmet Yavuz Selim Soyturk wrote:
> > > One temporary workaround that I considered for this problem
> > > would be to have eval() use introspection on its caller to
> > > create a "wrappe
On Wed, Dec 19, 2007 at 11:15:46PM +0100, Mehmet Yavuz Selim Soyturk wrote:
> > One temporary workaround that I considered for this problem
> > would be to have eval() use introspection on its caller to
> > create a "wrapper sub" that duplicates the lexical environment of
> > the caller, and then u
On Dec 19, 2007 5:30 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> - Modify Pmc2c so METHOD means the same thing as PCCMETHOD. (This change
> will need a deprecation cycle.)
> - Do a search-and-replace changing all instances of 'PCCMETHOD' to 'METHOD'.
FYI, These two items can be done any time p
Patch applied to trunk in r24102.
On Mon Dec 03 20:04:08 2007, [EMAIL PROTECTED] wrote:
> Uploading updated version of patch based on discussion with chromatic on
> perl6-internals mailing list.
Devin: This is the result I got when I applied the 2nd version of your
patch on Darwin and then ran the patched test file:
[parrot] 516
The immediate issue is resolved, so I'm resolving the ticket. Larger
issues about gcc should be dealt with in a new, separate ticket.
For better or worse, I haven't been getting these failures in recent
weeks, so I'm resolving the ticket.
No complaints; resolving ticket.
Paul Cochrane wrote:
Hi everyone,
these failures probably aren't critical for release, however I thought
it best to mention them.
Paul
System: Solaris 9
cc: Sun C 5.8 2005/10/13
Parrot revision: 24033
t/library/pcre...
# Failed test (t/library/pcre.t at line 35
Next month's development milestone is the implementation of the new PMC
spec. This milestone involves many small tasks, which can be divided up
pretty easily between a handful of people. Now that Jonathan's shipped
the release, here's a handful of tasks that could be picked off at
various skill
> One temporary workaround that I considered for this problem
> would be to have eval() use introspection on its caller to
> create a "wrapper sub" that duplicates the lexical environment of
> the caller, and then use that as the target of an :outer()
> flag when it's passed to imcc. For example,
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #48895]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=48895 >
This patch updates PLATFORMS for my Solaris 8 system, based on
parrot-0.5.1.
--- par
Allison Randal dijo [Wed, Dec 19, 2007 at 03:27:33PM +0200]:
>
> How difficult would it be to set up a debian-parrot group? It would
> consist of the specific Parrot team members who have responsibility
> for packaging and uploading Parrot (understanding that each would
> need to apply as a DM). W
Allison Randal dijo [Wed, Dec 19, 2007 at 02:14:35PM +0200]:
> Indeed. Parrot is a complete virtual machine similar to Mono or
> Java. As such, it's likely that Parrot will ultimately split into a
> few more packages than it currently has, including parrot-modules,
> parrot-dev, and packages for ru
On Mon Dec 03 20:04:08 2007, [EMAIL PROTECTED] wrote:
> Uploading updated version of patch based on discussion with chromatic on
> perl6-internals mailing list.
I spoke with Devin at the Perl 20th birthday celebration in New York
last night and he asked me to nudge this patch forward.
Can we get
Hello,
> Allison Randal wrote:
> > The Parrot release managers will adopt the Parrot Debian
> package. None
> > of our current release managers are Debian Developers, so
> we will need
> > to find a sponsor. Let us know if you have any recommendations.
>
> I CC'ed [EMAIL PROTECTED], I guess
Author: kjs
Date: Wed Dec 19 09:40:15 2007
New Revision: 24075
Modified:
trunk/docs/pdds/draft/pdd06_pasm.pod
Log:
[pdd06] change .constant into .macro_const
Modified: trunk/docs/pdds/draft/pdd06_pasm.pod
==
--- trunk
Jeremiah Foster wrote:
How difficult would it be to set up a debian-parrot group?
Not hard at all. As Martin mentioned, debian has a development machine
called alioth which hosts a GForge repository, if that is the right
word. http://alioth.debian.org/
This sounds like the ideal solution,
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #48877]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=48877 >
runtime/parrot/include/vtable_methods.pasm contains a great number of
.constant defini
> > In short, "teams" i.e. debian-perl are internal debian groups with
> > upload rights.
>
> How difficult would it be to set up a debian-parrot group?
Not hard at all. As Martin mentioned, debian has a development machine
called alioth which hosts a GForge repository, if that is the right
Jonathan Worthington wrote:
--
Lebennin
Silver flow the streams from Colos to Erui
In the green fields of Lebennin!
Tall grows the grass there. In the wind from the Sea
The white lilies sway,
And the golden bells are shaken of mallos and alfirin
In the green fields of Lebennin,
In the win
Klaas-Jan Stol wrote:
this sounds like a new sub :flag coming up...
The :multi flag already exists, so in this case just the implementation
will change.
Allison
On Dec 19, 2007 4:57 PM, Allison Randal <[EMAIL PROTECTED]> wrote:
> Francois PERRAD wrote:
> >
> > double__underscore still the only way to overload a non-vtable method,
> > for example, the opcode add (with MMD) :
>
thanks for the example.
>
>
> Ah, yes. I'll make a note of that in the MMD PDD
Francois PERRAD wrote:
double__underscore still the only way to overload a non-vtable method,
for example, the opcode add (with MMD) :
Ah, yes. I'll make a note of that in the MMD PDD I'm about to check in.
(It will change.)
Allison
> From: Allison Randal [mailto:[EMAIL PROTECTED]
>
> Indeed. Parrot is a complete virtual machine similar to Mono
> or Java. As such, it's likely that Parrot will ultimately
> split into a few more packages than it currently has,
> including parrot-modules, parrot-dev, and packages for
> ru
On Sun Dec 16 21:18:31 2007, coke wrote:
> From PDD19:
>
> =item .namespace [deprecated]
>
> Open a new scope block. This "namespace" is not the same as the
> .namespace [ ] syntax, which is used for storing
> subroutines
> in a particular namespace in the global symbol table.
> This directive
Klaas-Jan Stol wrote:
1. is the double__underscore thing still supposed to work and if so, is it
deprecated?
Deprecated, but not yet entirely removed from the code.
2. are the .constant definitions still needed? i.o.w., does updating that
file make sense or can i save myself that trouble.
> > Usually the debian maintainer is responsible for forwarding bugs,
> > since parrot is maintainer-less it appears that this didn't
> happen. I
> > will look into this and see if I can forward them.
>
> Thanks, that would be helpful.
Here is the first bug, it appears to be a debian bug an
Allison Randal wrote:
> The Parrot release managers will adopt the Parrot Debian package. None
> of our current release managers are Debian Developers, so we will need
> to find a sponsor. Let us know if you have any recommendations.
I CC'ed [EMAIL PROTECTED], I guess that's the right place to a
On Dec 19, 2007 10:27 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> How difficult would it be to set up a debian-parrot group? It would
> consist of the specific Parrot team members who have responsibility for
> packaging and uploading Parrot (understanding that each would need to
> apply as a D
This is a longish message describing some obstacles I'm
encountering with implementing eval() in perl6, especially
as it relates to handling of lexical (my) variables. IIRC
there are quite a few tests in the Perl 6/Pugs test suite
that expect a working eval(), so we may need this capability
sooner
Klaas-Jan Stol wrote:
in PIR you can override (or implement) a vtable method using the :vtable
flag.
before that, in the past, this was done by prefixing the vtable name with 2
underscores.
While ack'ing for ".constant" (to be replaced with .macro_const), I found
that the following file defines
in PIR you can override (or implement) a vtable method using the :vtable
flag.
before that, in the past, this was done by prefixing the vtable name with 2
underscores.
While ack'ing for ".constant" (to be replaced with .macro_const), I found
that the following file defines constants for all entrie
Jeremiah Foster wrote:
That document assumes that the team "parrot-porters" is a group of
debian developers working together to maintain parrot in debian, it is a
document aimed at debian developers. However I cannot find a debian team
called "parrot-porters". I assume this is the name that the
Jeremiah Foster wrote:
Parrot is a bit of different beastie than the perl modules we normally
handle. But I am fairly certain someone here would be willing to help. I
am not very familiar with parrot aside from having read some articles on
PIR and seen a couple talks, but it is still a bit over
The Parrot release managers will adopt the Parrot Debian package. None
of our current release managers are Debian Developers, so we will need
to find a sponsor. Let us know if you have any recommendations.
Also, is there any way we can get an upstream filing of the
Parrot-related requests to o
On Wednesday 19 December 2007 00:24:32 Paul Cochrane wrote:
> > [t] Nuked t/src/vtables.t, which pokes into the guts of libparrot using
> > functions not documented nor promised in the extension API. Making this
> > test work actually correctly in a sane and safe way would require either:
>
> Bet
chromatic,
> [t] Nuked t/src/vtables.t, which pokes into the guts of libparrot using
> functions not documented nor promised in the extension API. Making this test
> work actually correctly in a sane and safe way would require either:
Between 1/2 and 2/3 of the functions in src/vtables.c is act
41 matches
Mail list logo
