As I mentioned in RT #43481, the garbage collector does some dodgy flag
setting in memory pools, particularly in Parrot_add_to_free_list().
The attached patch fixes that, at least for PMC_EXT structures.
See src/gc/smallobject.c:210:
PObj_flags_SETTO((PObj *)object, PObj_on_free_list_FL
Hi,
considering the vast number of Operators and the like, I had the idea to
implement a tool where you can enter a small piece of p6 syntax, and it
explains what that might mean. (like a perldoc -f for operators/syntax
elements instead of functions)
A short example:
$ p6explain '[]'
[...] can be
Moritz Lenz skribis 2007-07-10 12:43 (+0200):
> $ p6explain '[]'
> [...] can be
> * '[$expression]': access to one or more array elements if used as
>postcircumfix
>Example: @a[2]; # access the third element of an array @a
> * '[$operator]': the 'reduce' hyper operator
>
* Anything else that should go into the requirements?
It would be even cooler if the command
$ p6explain 'some_user_defined_sub'
would display prettily-formatted pod for that sub and would work
transparently, regardless of whether this sub is defined in the Perl
standard library, CPAN module
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43709]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43709 >
In lib/Parrot/Docs/Group.pm there is the todo item:
# TODO - Groups should only co
Hi Amir,
Amir E. Aharoni wrote:
>> * Anything else that should go into the requirements?
>
> It would be even cooler if the command
>
> $ p6explain 'some_user_defined_sub'
>
> would display prettily-formatted pod for that sub and would work
> transparently, regardless of whether this sub is d
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43713]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43713 >
In the file lib/Parrot/Docs/Item.pm there is the todo item:
# TODO - Items should
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43717]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43717 >
in the file lib/Parrot/Op.pm there is the todo item (including the line of code)
s
(Sorry for personal message previously, now my answer to the list)
Juerd Waalboer wrote:
> Moritz Lenz skribis 2007-07-10 12:43 (+0200):
>> $ p6explain '[]'
>> [...] can be
>> * '[$expression]': access to one or more array elements if used as
>>postcircumfix
>>Example: @a[2];
Just updating this ticket to the current state of play:
> The lint target needs to be renamed to splint.
Actually, this has been changed to sunlint and bsdlint. The splint
target has existed for a while (in two forms; now combined as of r19721
into the one target).
> Then create a new lint ta
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43715]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43715 >
In the file lib/Parrot/Docs/POD2HTML.pm there is the todo item:
# TODO - C sho
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43719]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43719 >
In the file lib/Parrot/OpsFile.pm there is the todo item:
# TODO: Complain abo
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43721]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43721 >
In the file lib/Parrot/OpsFile.pm there is the todo item:
# FIXME: This ought
Moritz Lenz <[EMAIL PROTECTED]> writes:
> Hi,
>
> considering the vast number of Operators and the like, I had the
> idea to implement a tool where you can enter a small piece of p6
> syntax, and it explains what that might mean. (like a perldoc -f for
> operators/syntax elements instead of functio
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43723]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43723 >
In the file lib/Parrot/PIR/Formatter.pm there is the todo item:
# XXX we should check
Steffen Schwigon wrote:
> Moritz Lenz <[EMAIL PROTECTED]> writes:
>> considering the vast number of Operators and the like, I had the
>> idea to implement a tool where you can enter a small piece of p6
>> syntax, and it explains what that might mean. (like a perldoc -f for
>> operators/syntax eleme
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43729]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43729 >
In the file lib/Parrot/Pmc2c.pm, there is the todo item within the
init() method:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43731]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43731 >
In the file lib/Parrot/Pmc2c.pm there is the todo item associated with
the calltype has
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43733]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43733 >
In the file lib/Parrot/Pmc2c.pm there is the todo item:
# TODO
# scan src/call
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43737]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43737 >
In the file lib/Parrot/Pmc2c.pm there is the todo item:
# XXX quick hack - to get MMD
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43727]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43727 >
In the file lib/Parrot/Pmc2c.pm there is the todo item:
# FIXME support getting im
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43741]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43741 >
In the file lib/Parrot/Pmc2c.pm there is the todo item (within the
vtable_decl() sub):
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43739]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43739 >
In the file lib/Parrot/Pmc2c.pm there is the todo item:
$self->{mmds} = @mmds;
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43735]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43735 >
In the file lib/Parrot/Pmc2c.pm there is the todo item (within the
proto() method):
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43745]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43745 >
In the file lib/Parrot/Pmc2c/Pmc2cMain.pm there is the todo item:
# XXX t
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43725]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43725 >
In the file lib/Parrot/Pmc2c.pm there is the todo item:
# autogenerate for exo
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43751]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43751 >
In the file lib/Parrot/Test.pm there is the todo item:
# XXX put this into sub
Hi all,
I've found that when using the Opera web browser that I can't edit any
parrot wiki pages. I click on the "Edit" button, a hash character (#)
gets appended to the URL, and nothing else happens. I've only had
success at editing the wiki pages with firefox, but it'd be nice to be
able to u
# New Ticket Created by Jerry Gay
# Please include the string: [perl #43757]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43757 >
i made some small local mods while trying to debug a segfault during
'make test' for langua
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43753]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43753 >
In the file lib/Parrot/Test.pm there is the todo item:
# TODO: $langua
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43755]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43755 >
In the file lib/Parrot/Test.pm there is the todo item:
# XXX this is broken WRT to
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43749]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43749 >
In the file lib/Parrot/Pmc2c/StmRef.pm there is the todo item:
if ( $self->does_wr
# New Ticket Created by Jerry Gay
# Please include the string: [perl #43759]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43759 >
below is the results from running the subversion command to list the
status of a working co
# New Ticket Created by "brian d foy"
# Please include the string: [perl #43761]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43761 >
Some of the Perl::Critic modules are still in the Parrot distro, but
they don't belong
Steffen Schwigon wrote:
Do you think it's possible to extract and collect all the operators
and descriptions from the synopses into one common place?
The problem with that is that it wouldn't scale to user-defined
operators/macros. I think the way to approach it would be to define a
POD6 dial
On Tuesday 10 July 2007 09:43:28 brian d foy wrote:
> Some of the Perl::Critic modules are still in the Parrot distro, but
> they don't belong (in the PAUSE sense) to Parrot. This patch tells the
> PAUSE indexer not to look at them.
>
> If you can get this patch in before today's release, then the
Author: allison
Date: Tue Jul 10 13:27:44 2007
New Revision: 19772
Modified:
trunk/docs/pdds/draft/pdd17_pmc.pod
Log:
[pdd] Archiving conversation about new way of instantiating builtin PMCs after
numeric type system goes away.
Modified: trunk/docs/pdds/draft/pdd17_pmc.pod
==
Author: allison
Date: Tue Jul 10 13:36:22 2007
New Revision: 19773
Modified:
trunk/docs/pdds/draft/pdd17_pmc.pod
Log:
[pdd] Saving discussion about dynamically extending PMCs from PIR.
Modified: trunk/docs/pdds/draft/pdd17_pmc.pod
=
Dave Whipp wrote:
> Steffen Schwigon wrote:
>> Do you think it's possible to extract and collect all the operators
>> and descriptions from the synopses into one common place?
>
> The problem with that is that it wouldn't scale to user-defined
> operators/macros.
You're probably right about tha
I've found that when using the Opera web browser that I can't edit any
parrot wiki pages. I click on the "Edit" button, a hash character (#)
gets appended to the URL, and nothing else happens. I've only had
success at editing the wiki pages with firefox, but it'd be nice to be
able to use more b
On Jul 10, 2007, at 4:44 PM, Paul Cochrane wrote:
I've found that when using the Opera web browser that I can't edit
any
parrot wiki pages. I click on the "Edit" button, a hash character
(#)
gets appended to the URL, and nothing else happens. I've only had
success at editing the wiki page
On 11/07/07, Jesse Vincent <[EMAIL PROTECTED]> wrote:
On Jul 10, 2007, at 4:44 PM, Paul Cochrane wrote:
>> I've found that when using the Opera web browser that I can't edit
>> any
>> parrot wiki pages. I click on the "Edit" button, a hash character
>> (#)
>> gets appended to the URL, and noth
Moritz Lenz wrote:
You're probably right about that, but somebody who writes his own macros
and operators probably doesn't need such a tool anyway. And should write
very good documentation, otherwise he has lost outright.
(I was thinking that your tool would provide a mechanism for them to
pro
Author: larry
Date: Tue Jul 10 17:39:45 2007
New Revision: 14428
Modified:
doc/trunk/design/syn/S05.pod
Log:
The ** form is now syntactically independent of the following token.
This allows us to distinguish literal counts and ranges from indirect ones
specified via closure. It also allows a
On Tue, Jul 10, 2007 at 04:37:13PM -0700, Dave Whipp wrote:
: One approach would simply be to edit Perl-6.0.0-STD.pm and add some
: markup. To pick a token at random:
:
: =p6explain *
: An asterix in a version expression matches any version
: =end
: token whatever { '*' {*} }
Indeed, the example
Author: larry
Date: Tue Jul 10 18:20:25 2007
New Revision: 14429
Modified:
doc/trunk/design/syn/S05.pod
Log:
Clarify that all quantifier modifiers now attach directly to the **
Modified: doc/trunk/design/syn/S05.pod
On Fri Jun 29 01:52:18 2007, richard at rusrating.ru wrote:
> Dear Parrot people,
>
> Just updates my subversion depository after a long time.
>
> Got this error after 'make'
Richard - it is often necessary after a long break between updates to run 'make
realclean' before
doing a configure/m
Discussion on IRC today about how we can improve the state of the GC
system. One of the things that came up was that perhaps we shouldn't
be poking inside PMC guts outside of src/*pmc/: instead, we should be
using vtable access.
I currently see ~500 instances where we use PMC_data() outside
# New Ticket Created by Will Coleda
# Please include the string: [perl #43775]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43775 >
This transaction appears to have no content
Author: larry
Date: Tue Jul 10 18:45:08 2007
New Revision: 14430
Modified:
doc/trunk/design/syn/S09.pod
Log:
Some thinking about how .keys and .shape work on user-defined dimensions
Modified: doc/trunk/design/syn/S09.pod
===
It is now possible to open tickets from the command line if you're a bugadmin.
First, get an RT
CLI account; see the wiki for details. Then:
rt create -e -t ticket set subject='Testing new ticket' [EMAIL PROTECTED]
Queue=parrot
Will pop you into an editor. Add your text message at the end (any
# New Ticket Created by Will Coleda
# Please include the string: [perl #43779]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43779 >
Here's another test ticket. Line needs to have some leading whitespace?
And one more?
52 matches
Mail list logo
