Patrick R. Michaud wrote:
I just want to add a reminder here that the whole reason PCT,
PAST-pm, and Tcl use morph in the first place is because Parrot
doesn't provide a usable replace pmc with clone opcode, and
using morph+assign is a workaround.
In other words, if a replace pmc opcode exists,
Author: allison
Date: Sun Nov 25 04:02:44 2007
New Revision: 23030
Modified:
trunk/docs/pdds/pdd25_concurrency.pod
Log:
[pdd] More details on the structure and API for Scheduler and Task PMCs.
Modified: trunk/docs/pdds/pdd25_concurrency.pod
Author: allison
Date: Sun Nov 25 04:15:55 2007
New Revision: 23032
Modified:
trunk/docs/pdds/draft/pdd19_pir.pod
Changes in other areas also in this revision:
Modified:
trunk/docs/imcc/calling_conventions.pod
Log:
[pdd] Moving content from IMCC docs to PIR PDD.
Modified:
Author: allison
Date: Sun Nov 25 04:20:21 2007
New Revision: 23033
Modified:
trunk/docs/pdds/pdd17_pmc.pod
Log:
[pdd] Adding a pmclass modifier for role conflict resolution (partial).
Modified: trunk/docs/pdds/pdd17_pmc.pod
On Sat Nov 24 13:26:01 2007, bernhard wrote:
On Mi. 05. Jul. 2006, 12:17:12, bernhard wrote:
Contrive things so that no code whatsover must be maintained outside
of the language specific directory. This includes:
[snip]
config/gen/languages.pm handles the configuration of languages.
On Sun, Nov 25, 2007 at 01:56:51PM +0200, Allison Randal wrote:
Patrick R. Michaud wrote:
I just want to add a reminder here that the whole reason PCT,
PAST-pm, and Tcl use morph in the first place is because Parrot
doesn't provide a usable replace pmc with clone opcode, and
using
What's the difference between CONST_STRING and string_from_literal?
In particular, which one should be used when? In some code I see
things like:
# src/pmc/exporter.pmc
STRING *s_hash = CONST_STRING(interp, hash);
and in others we have
# src/pmc/codestring.pmc
STRING
In article [EMAIL PROTECTED], Patrick R.
Michaud [EMAIL PROTECTED] wrote:
How others can start hacking and contributing
-
If you're interested in hacking on the compiler, my suggestion
is to become somewhat familiar with the compiler tools
On Sunday 25 November 2007 07:15:01 Patrick R. Michaud wrote:
What's the difference between CONST_STRING and string_from_literal?
In particular, which one should be used when? In some code I see
things like:
# src/pmc/exporter.pmc
STRING *s_hash = CONST_STRING(interp, hash);
# New Ticket Created by James Keenan
# Please include the string: [perl #47792]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47792
While running Configure.pl on Linux today, I repeatedly got this error:
This bug is also preventing me from successfully calling 'make realclean':
/usr/local/bin/perl -MExtUtils::Command -e rm_f \
runtime/parrot/dynext/*.so \
runtime/parrot/dynext/*.so \
runtime/parrot/dynext/*.lib \
*.pdb runtime/parrot/dynext/*.pdb \
*.ilk
On 25/11/2007, via RT James Keenan [EMAIL PROTECTED] wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #47792]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47792
While running
On Sun, Nov 25, 2007 at 09:19:20AM -0800, chromatic wrote:
On Sunday 25 November 2007 07:15:01 Patrick R. Michaud wrote:
What's the difference between CONST_STRING and string_from_literal?
In particular, which one should be used when? In some code I see
things like:
#
If you're interested in hacking on the compiler, my suggestion
is to become somewhat familiar with the compiler tools already
available in Parrot.
I'm not interested in hacking on the compiler, but I am interested in
writing tests. I've added some to the Pugs project, but that seems
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #47794]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47794
The :method flag on subs doesn't seem to work when
the :outer flag is
On Sunday 25 November 2007 10:35:01 Patrick R. Michaud wrote:
On Sun, Nov 25, 2007 at 09:19:20AM -0800, chromatic wrote:
CONST_STRING() is 100% more awesome, because it's completely constant.
[...]
PDD 15 branch after replacing string_from_literal() with CONST_STRING().
We should do
On Sunday 25 November 2007 04:23:59 [EMAIL PROTECTED] wrote:
Added:
trunk/include/parrot/scheduler.h (contents, props changed)
trunk/src/pmc/scheduler.pmc (contents, props changed)
trunk/src/pmc/task.pmc (contents, props changed)
trunk/t/pmc/scheduler.t (contents, props
On Sun, Nov 25, 2007 at 11:50:15AM -0800, chromatic wrote:
On Sunday 25 November 2007 10:35:01 Patrick R. Michaud wrote:
On Sun, Nov 25, 2007 at 09:19:20AM -0800, chromatic wrote:
CONST_STRING() is 100% more awesome, because it's completely constant.
[...]
PDD 15 branch after
On Sunday 25 November 2007 12:37:13 Patrick R. Michaud wrote:
On Sun, Nov 25, 2007 at 11:50:15AM -0800, chromatic wrote:
It doesn't *always* work. For example, I think CONST_STRING() doesn't
work in PCCMETHODs in PMCs for some reason I can't explain, and it
doesn't work in other source
On Sun, Nov 25, 2007 at 12:57:35PM -0800, chromatic wrote:
On Sunday 25 November 2007 12:37:13 Patrick R. Michaud wrote:
On Sun, Nov 25, 2007 at 11:50:15AM -0800, chromatic wrote:
It doesn't *always* work. For example, I think CONST_STRING() doesn't
work in PCCMETHODs in PMCs for
On Nov 25, 2007, at 12:52 PM, Paul Cochrane via RT wrote:
This error has been happening in dotnet for a long time. I can't give
you a better timeframe than that, but it's been in that state (giving
these warnings) since before I managed to get it's Configure.pl to go
again, (which was a
On Sun Nov 25 09:52:45 2007, ptc wrote:
This error has been happening in dotnet for a long time. I can't give
you a better timeframe than that, but it's been in that state (giving
these warnings) since before I managed to get it's Configure.pl to go
again, (which was a few months ago now).
On 25/11/2007, James E Keenan [EMAIL PROTECTED] wrote:
On Nov 25, 2007, at 12:52 PM, Paul Cochrane via RT wrote:
This error has been happening in dotnet for a long time. I can't give
you a better timeframe than that, but it's been in that state (giving
these warnings) since before I
On Sun, Nov 25, 2007 at 03:09:22PM -0800, [EMAIL PROTECTED] wrote:
Log:
[tools] Allow other double-quoted strings in a line with the CONST_STRING()
macro, as long as there's an even number of quotes. This (still) doesn't work
if there's an escaped double-quote, but it never did and it hasn't
Hi,
here/hear, hear/here, on the 'ghost town' point... it's an immense surprise
given the size of CPAN that there is such a 'ghost town' feel about some (if
not all) of Perl6...
Regards,
K
On Nov 25, 2007 2:58 PM, brian d foy [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED], Patrick R.
# New Ticket Created by Will Coleda
# Please include the string: [perl #47816]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47816
Yet another tcl segfault, this time on feather. (linux)
Revision: 23055
1) build
# New Ticket Created by Will Coleda
# Please include the string: [perl #47822]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47822
The generated a.pir file is generating code like:
.local float foo
instead of
On Sun Nov 25 15:05:59 2007, ptc wrote:
I too am running Configure.pl constantly, however, not dotnet's
Configure.pl. This is the script I was referring to.
Well, now it's happening in ./Configure.pl -- which means we have a big
problem, because everyone who configures is going to see it.
r23011 added code to config/gen/languages.pm to configure dotnet when
configuring parrot
instead of (as before) manually, after parrot was built.
This isn't ready to happen yet. Reverting 23011 in spirit, dotnet is on its own
again.
fixed in r23065.
On Wed Oct 31 13:21:19 2007, [EMAIL PROTECTED] wrote:
Subject: [BUG] Segfault after parallell build
Sorry, didn't read the output carefully enough: it's a compilation
error, not a segfault. The other informations should be accurate ;)
This is due to the fact that there are items in
On Sun Nov 25 20:10:02 2007, coke wrote:
On Wed Oct 31 13:21:19 2007, [EMAIL PROTECTED] wrote:
Subject: [BUG] Segfault after parallell build
Sorry, didn't read the output carefully enough: it's a compilation
error, not a segfault. The other informations should be accurate ;)
This is
On Sat Sep 01 02:32:28 2007, bernhard wrote:
In languages/lisp/system.pir there are 4 unused PMCs declared.
Removing one of them breaks Lisp.
Here is an example session:
[EMAIL PROTECTED]:~/devel/Parrot/repos/parrot/languages/lisp$ svn diff
Index: system.pir
# New Ticket Created by Will Coleda
# Please include the string: [perl #47826]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47826
The NCI information in docs/books is out of date. per codyl on
#parrot, the code
On Tue Mar 13 12:44:33 2007, particle wrote:
in order to help find some long-standing garbage collector bugs, in
r17470 i've just disabled the -G flag on three PGE test files. see the
content of the patch below. this may cause test failures due to a gc
bug.
this ticket serves to notify
34 matches
Mail list logo
