Re: svn commits via email missing?

On Sun, Oct 05, 2008 at 10:43:45AM -0500, Patrick R. Michaud wrote: > We seem to have lost the svn-commit mail updates, I haven't seen > a svn-commit message since r31606 on October 3 (parrot is > currently at r31676). > > Any chance we get could this back? For me it's much easier to > review

Re: [svn ci] added support for decorators to pmc methods

On Aug 7, 2007, at 1:38 PM, chromatic wrote: Are there any cases where they *can* be NULL? I wonder if slapping NOTNULL() on them by default would break anything. (I can't think of anything that's not already a bug.) But can't some PMC methods take additional args, besides the default

Re: [svn ci] added support for decorators to pmc methods

On Tuesday 07 August 2007 11:29:03 Andy Lester wrote: > What about being able to do NOTNULL() and NULLOK() on args to the > PMC? For the decorators to really make sense, we need both halves of > the equation. Are there any cases where they *can* be NULL? I wonder if slapping NOTNULL() on them

Re: [svn ci] added support for decorators to pmc methods

On Aug 7, 2007, at 1:26 PM, jerry gay wrote: as of r20545, you can now decorate pmc methods to give the compiler a hand in warning you about bad code, just like we've been doing throughout parrot core (a.k.a. seatbelts.) for a list of decorators, see include/parrot/compiler.h. for more info, se

Re: svn r18461 indentation problem?

Mark, It's highly likely that I was wrong to indent your example. I've noticed that particle has done some more work on the pod and he's moved it back :-) Anyway, your work is now in. Good stuff! Thanks for the help! Paul On 08/05/07, Mark Glines <[EMAIL PROTECTED]> wrote: Hi Paul! I not

Re: Ease of Committing Tests (was Re: [svn ci] NCI methods now name-mangled)

On Apr 6, 2007, at 11:48 AM, chromatic wrote: On Friday 06 April 2007 00:58, Joshua Isom wrote: What if we had a repository, ala pugs with it's "open" commits, solely for people to commit tests.  It could help improve bug discovery and test coverage, as well as ambiguity about features in par

Ease of Committing Tests (was Re: [svn ci] NCI methods now name-mangled)

On Friday 06 April 2007 00:58, Joshua Isom wrote: > What if we had a repository, ala pugs with it's "open" commits, solely > for people to commit tests.  It could help improve bug discovery and > test coverage, as well as ambiguity about features in parrot.  Then > developers could just update it

Re: [svn ci] NCI methods now name-mangled

On Apr 5, 2007, at 5:45 PM, Leopold Toetsch wrote: Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington: Don't really need a policy to tell me that breaking stuff for languages folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips through the net occasionally. In t

Re: [svn ci] NCI methods now name-mangled

Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington: > Don't really need a policy to tell me that breaking stuff for languages > folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips > through the net occasionally. In this case, I wasn't even aware that you > could use

Re: [svn ci] PMC documentation guidelines draft

Joshua Isom wrote: On Apr 5, 2007, at 10:45 AM, Klaas-Jan Stol wrote: jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs.

Re: [svn ci] PMC documentation guidelines draft

On Apr 5, 2007, at 10:45 AM, Klaas-Jan Stol wrote: jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs. you'll find the docu

Re: [svn ci] PMC documentation guidelines draft

jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs. you'll find the document at docs/pmc/documentation.pod. highlights: ~ br

Re: [svn ci] NCI methods now name-mangled

Jonathan Worthington wrote: Anyway, fixed in r17982. May need a realclean - I had to do one anyway to run the buildtools tests. Awesome. Works for me even without realclean. Thanks! Allison

Re: [svn ci] NCI methods now name-mangled

Allison Randal wrote: This is a leftover from the old days when the way to override a vtable method was to define a method with an '__' name, so they never conflicted. Not really - this was a conflict in the names of the methods at a C level. The '__' prefix was a PIR-level thing. In PIR we ma

Re: [svn ci] NCI methods now name-mangled

Allison Randal wrote: For me too, even after a 'make realclean' on Parrot. In the interests of our developing policy on a stable trunk: Jonathan, fix the problem for Lua or revert the change before continuing with further development. Don't really need a policy to tell me that breaking stuff for

Re: [svn ci] NCI methods now name-mangled

François PERRAD wrote: This new behavior breaks the build of Lua PMC. Argh, sorry. :-( Thanks for the detailed bug report - I know where the problem is, and am working on a fix. Jonathan

Re: [svn ci] NCI methods now name-mangled

Jonathan Worthington wrote: Hi, I was working on starting to move class functionality into v-table methods, as discussed on list recently. However, I hit an interesting issue - you cannot have a METHOD or PCCMETHOD with the same name as a vtable method. We need to be able to do that to implem

Re: [svn ci] NCI methods now name-mangled

François PERRAD wrote: Anyway, hope this is agreeable, and please do report any issues. This new behavior breaks the build of Lua PMC. For me too, even after a 'make realclean' on Parrot. In the interests of our developing policy on a stable trunk: Jonathan, fix the problem for Lua or reve

Re: [svn ci] NCI methods now name-mangled

At 01:33 04/04/2007 +0100, Jonathan Worthington wrote: Hi, I was working on starting to move class functionality into v-table methods, as discussed on list recently. However, I hit an interesting issue - you cannot have a METHOD or PCCMETHOD with the same name as a vtable method. We need to b

Re: SVN tips in wranglers.pod

On 11/7/06, Paul Cochrane <[EMAIL PROTECTED]> wrote: Thanks Bernhard! Added to the list. Paul > When the commit is associated with a ticket in RT, I usually copy&paste the > ticket header. e.g. > > #39197: [CAGE] lib/Parrot/Test.pm ignores core dumps failures!CU, > > Bernhard paul~ i to

Re: SVN tips in wranglers.pod

Thanks Bernhard! Added to the list. Paul When the commit is associated with a ticket in RT, I usually copy&paste the ticket header. e.g. #39197: [CAGE] lib/Parrot/Test.pm ignores core dumps failures!CU, Bernhard

Re: SVN tips in wranglers.pod

Paul Cochrane schrieb: In the attached patch, I've added a section on SVN usage tips for the doc/dev/wranglers.pod documentation, mostly distilled from wisdom on #parrot. Is there anything else people think should be added before I commit the patch? Or any changes to the pod itself? When the c

Re: SVN::Web

Hi Nik, * Nik Clayton <[EMAIL PROTECTED]> [2006-05-12 15:40]: > Mea culpa -- that was supposed to be an e-mail. well, that’s what it was, too. Regards, -- Aristotle Pagaltzis //

Re: SVN::Web

Nik Clayton wrote: Nik Clayton wrote: Hi Adam, [...] Mea culpa -- that was supposed to be an e-mail. N That's totally fine. :) I used Insurrection because it was there... and I didn't know of anything else that worked. And once you get past the fact that it's impossible to install, it d

Re: SVN::Web

Nik Clayton wrote: Hi Adam, [...] Mea culpa -- that was supposed to be an e-mail. N

Re: SVN::Web

Nik Clayton wrote: Hi Adam, Adam Kennedy wrote: Phase N is my company, and http://svn.phase-n.com/svn/cpan is the collaborative subversion repository for my code, that now includes PPI, which you've expressed a desire to have bugs fixed in I believe a number of times. I see you're using Ins

Re: svn links for the Architecture section on the website?

> Given the recent explosion of svn commits in the synopses, and the fact that > the versions of the synopses on the dev.perl.org/perl6 site are lagging a > bit, would it make sense to add a link to the svn site to the > Synopses page? I'd rather not. The ones on the dev site shouldn't have be

Re: svn performance

On Sat, 4 Mar 2006, Leopold Toetsch wrote: > > On Feb 28, 2006, at 19:27, Andy Dougherty wrote: > > > > > Executive summary -- svn co on Solaris 8 is still *slow*! I"ll stick > > to fetching snapshots with wget. > > Dumb question? Why 'svn co' instead of incrementally updating with 'svn up'?

Re: svn performance

On Feb 28, 2006, at 19:27, Andy Dougherty wrote: Executive summary -- svn co on Solaris 8 is still *slow*! I"ll stick to fetching snapshots with wget. Dumb question? Why 'svn co' instead of incrementally updating with 'svn up'? leo

Re: svn performance

> On Fri, Feb 17, 2006 Andy Dougherty wrote: [svn co on Solaris 8 is painfully *slow*] > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > real0m16.84s > user0m0.09s > sys 0m0.20s > > $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk > > real 2:0

Re: svn performance

On Fri, Feb 17, 2006 at 05:23:55PM -0500, Andy Dougherty wrote: > On Fri, 17 Feb 2006, jesse wrote: > > Do you, perchance, sit behind an http proxy server? > > Not that I know of (though I'm not sure how I'd know), and no other mode > of communication is similarly affected (i.e. cvs, rsync, etc.,

Re: svn performance

From: Andy Dougherty <[EMAIL PROTECTED]> Date: Fri, 17 Feb 2006 17:23:55 -0500 (EST) On Fri, 17 Feb 2006, jesse wrote: > Try: > time svn co https://svn.perl.org/parrot/trunk parrot-trunk svn: Unrecognized URL scheme 'https://svn.perl.org/parrot/trunk' I don't know why. I

Re: svn performance

On Fri, 17 Feb 2006, jesse wrote: > > > On Fri, 17 Feb 2006, Matt Fowles wrote: > > > > > > > > On 2/17/06, Andy Dougherty <[EMAIL PROTECTED]> wrote: > > > > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > > > real0m16.84s > > > > $ time svn co http://svn.perl.org/

Re: svn performance

On 2/17/06, Matt Fowles <[EMAIL PROTECTED]> wrote: > $ svn --version > svn, version 1.1.4 (r13838) >compiled May 13 2005, 06:29:47 > > How bout you? > can't hurt to upgrade... >svn --version svn, version 1.3.0 (r17949) compiled Jan 15 2006, 23:18:48 ~jerry

Re: svn performance

> On Fri, 17 Feb 2006, Matt Fowles wrote: > > > > > On 2/17/06, Andy Dougherty <[EMAIL PROTECTED]> wrote: > > > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > > real0m16.84s > > > $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk > > > real 2:01:50.3 > >

Re: svn performance

On Fri, 17 Feb 2006, Matt Fowles wrote: > > On 2/17/06, Andy Dougherty <[EMAIL PROTECTED]> wrote: > > Sigh. I wish it were that simple, or that funny. > > > > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > > > real0m16.84s > > user0m0.09s > > sys 0m0.20s >

Re: svn performance

Andy~ On 2/17/06, Andy Dougherty <[EMAIL PROTECTED]> wrote: > On Fri, 17 Feb 2006, Matt Fowles wrote: > > > All~ > > > > On 2/17/06, jesse <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On Fri, Feb 17, 2006 at 08:38:26AM -0800, Robert Spier wrote: > > > > > snapshots or releases. And, since a

Re: svn performance

> Sigh. I wish it were that simple, or that funny. > > $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz > > real0m16.84s > user0m0.09s > sys 0m0.20s > > $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk > > real 2:01:50.3 > user 1:02.0 > sys

Re: svn performance

On Fri, 17 Feb 2006, Matt Fowles wrote: > All~ > > On 2/17/06, jesse <[EMAIL PROTECTED]> wrote: > > > > > > > > On Fri, Feb 17, 2006 at 08:38:26AM -0800, Robert Spier wrote: > > > > snapshots or releases. And, since a checkout takes about an hour (last > > > > time I checked) I tend to be too la

Re: svn performance

All~ On 2/17/06, jesse <[EMAIL PROTECTED]> wrote: > > > > On Fri, Feb 17, 2006 at 08:38:26AM -0800, Robert Spier wrote: > > > snapshots or releases. And, since a checkout takes about an hour (last > > > time I checked) I tend to be too lazy to fetch one just to make a patch. > > > > Only if you'r

Re: svn performance

On Fri, Feb 17, 2006 at 08:38:26AM -0800, Robert Spier wrote: > > snapshots or releases. And, since a checkout takes about an hour (last > > time I checked) I tend to be too lazy to fetch one just to make a patch. > > Only if you're checking out to a Commodore 64. Or possibly hand-transcri

Re: [svn ci] Better gdb support (r11581)

Leopold Toetsch wrote: A debug session snippet: I've changed the syntax now to the more conforming convenience var syntax for registers: (gdb) pp $I1 I1=3 $x0 ... $x9 are predefined for x in S,I,N (no PMCs yet) This is the same as printing HW registers: (gdb) p $eax $1 = 135154512 And:

Re: svn access (was: [perl #38576] [PATCH] Make DETAIL_MEMORY_DEBUG work. )

On Wed, 15 Feb 2006, Leopold Toetsch via RT wrote: > Andy, I've already asked once: don't you have svn access? If no (and if > you want it) please mail me your auth.perl.org account data, to get you > svn priv bits. I do have priv bits, and have on rare occasion used them, but I don't usually

Re: [svn ci] Changes to dynoplibs build process

"Nick Glencross" <[EMAIL PROTECTED]> wrote: On 1/10/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > I would really like some feedback from MinGW and cygwin folks on how > dynoplibs build and work for them Works straight off on cygwin. :-) Gives the answers you wanted. That's great, thank

Re: [svn ci] Changes to dynoplibs build process

On 1/10/06, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > "Jonathan Worthington" <[EMAIL PROTECTED]> wrote: > > Note that dynamic op libs do not *work* on Win32 yet > They do now - I'm using them with my .NET to PIR translator and they work > nicely. > > I would really like some feedback from M

Re: [svn ci] Changes to dynoplibs build process

"Jonathan Worthington" <[EMAIL PROTECTED]> wrote: Note that dynamic op libs do not *work* on Win32 yet They do now - I'm using them with my .NET to PIR translator and they work nicely. I would really like some feedback from MinGW and cygwin folks on how dynoplibs build and work for them, as I

Re: Svn Commit list...

> ... seems to be dead for about a day now, though I know commits are > going through. Fixed. > BCCing webmaster at perl dot org, where this will hopefully open a > ticket. THANK YOU. This meant the message got seen much earlier than it otherwise would, and because of the BCC, no collateral dam

Re: [svn ci] Perl 5 tests for PGE::P5Regexp (update)

On 11/21/05, jerry gay <[EMAIL PROTECTED]> wrote: > i've checked in a subset of Perl 5.9.2's regexp tests for PGE to chew > on. for now, i modified the stolen harness to emit PIR. the harness is > currently very ugly... that won't be for long, however, as i'll > refactor it soon. > it's been refact

Re: [svn ci] Debug segment updates

"Jonathan Worthington" <[EMAIL PROTECTED]> wrote: What's left? Making this work for when you .include files in PIR. Which means monkeying with the lexer and IMCC. I've done it and it's available to play with. I'll admit now that, despite having covered quite a bit of the IMCC codebase whi

Re: [svn ci] (r8717) Win32 Dynclasses

Woot! None of the tests are currently failing on OS X, though there are several TODOs hey. Many (All??) of the failing tests are TODOs: perhaps the test harness isn't happy about TODOs on win32, for some reason. Do TODO tests report as passed in the core suite? If so, it's probably

Re: SVN revision (was: [perl #xxxxxx] Badly balanced at classes/pmc2c2.pl)

On Monday 11 April 2005 17:54, Leopold Toetsch wrote: > BTW: a nice to have: include SVN revision of local copy in bug report. I'll implement it. jens

Re: svn

On Thu, 9 Dec 2004, Michael G Schwern wrote: On Thu, Dec 09, 2004 at 04:35:26PM -0800, Brent 'Dax' Royal-Gordon wrote: Michael G Schwern <[EMAIL PROTECTED]> wrote: 1) Are they easily available on all the platforms Parrot is? Various Unixen, OS X, Windows. Is there any hope for a VMS port? Can w

Re: svn

On Thu, Dec 09, 2004 at 04:35:26PM -0800, Brent 'Dax' Royal-Gordon wrote: > Michael G Schwern <[EMAIL PROTECTED]> wrote: > > 1) Are they easily available on all the platforms Parrot is? Various > > Unixen, OS X, Windows. Is there any hope for a VMS port? > > Can we add "are there GUIs for Windo

Re: svn

Michael G Schwern <[EMAIL PROTECTED]> wrote: > 1) Are they easily available on all the platforms Parrot is? Various > Unixen, OS X, Windows. Is there any hope for a VMS port? Can we add "are there GUIs for Windows, OS X, and other platforms with wimpy users?" ;^) -- Brent 'Dax' Royal-Gordon

Re: svn

On Wed, Dec 08, 2004 at 07:19:07PM -0500, William Coleda wrote: > Is there a plan at any point to move to an svn repository from cvs? > > I'd like to work on a patch to move all the perl* pmcs into dynclasses, > which would involve quite a bit of file moving, and I'll happily wait for > svn if w

Re: svn

On Wed, Dec 08, 2004 at 06:21:18PM -0700, Phil Frost wrote: > On Wed, Dec 08, 2004 at 07:19:07PM -0500, William Coleda wrote: > > Is there a plan at any point to move to an svn repository from cvs? > > > > I'd like to work on a patch to move all the perl* pmcs into dynclasses, > > which would inv

Re: svn

William Coleda wrote: I'd like to work on a patch to move all the perl* pmcs into dynclasses, which would involve quite a bit of file moving, Hi, I'm currently working on moving the implementation of the PerlHash PMC into a Hash PMC. The plan is to let PerlHash be an extension of Hash. Currentl

Re: svn

On Wed, Dec 08, 2004 at 10:16:21PM -0500, Matt Fowles wrote: > While I personally like the idea, I think it is unlikely given how > much slower svn is on sizable repositories. Of course I have not > tried it recently, so maybe that has changed... If you wish to try out a recent Subversion on some

Re: svn

> While I personally like the idea, I think it is unlikely given how > much slower svn is on sizable repositories. Of course I have not > tried it recently, so maybe that has changed... > All that being said, I am in absolutely no position of authority about this... This is, and always has been,

Re: svn

Will~ On Wed, 08 Dec 2004 19:19:07 -0500, William Coleda <[EMAIL PROTECTED]> wrote: > Is there a plan at any point to move to an svn repository from cvs? > > I'd like to work on a patch to move all the perl* pmcs into dynclasses, which > would involve quite a bit of file moving, and I'll happil