63173a3..572f474 100644
> > --- a/build/gen_parrot.pl
> > +++ b/build/gen_parrot.pl
> > @@ -43,12 +43,6 @@ close $REQ;
> > }
> > }
> >
> > -print "Checking out Parrot r$reqsvn via svn...\n";
> > -system_or_die(qw(svn checkout -r
On Wed, Jul 28, 2010 at 4:58 AM, Will Coleda via RT
wrote:
> On Tue Jun 15 00:11:43 2010, q...@cono.org.ua wrote:
>> perl Configure.pl --gen-parrot failed time to time. Need to do
>> realclean before update.
> +1 on this patch (at least in spirit) from me, but I cannot apply it
> (probably becau
On Wed, Jul 28, 2010 at 4:58 AM, Will Coleda via RT
wrote:
>
> +1 on this patch (at least in spirit) from me, but I cannot apply it
> (probably because it was
> inlined in the ticket.) Can you add it as an attachment?
>
> Thanks!
in attachment
--
Varyanick I. Alex
icq: 102 575 440
skype: cono.
b/build/gen_parrot.pl
> @@ -43,12 +43,6 @@ close $REQ;
> }
> }
>
> -print "Checking out Parrot r$reqsvn via svn...\n";
> -system_or_die(qw(svn checkout -r), $reqsvn ,
> qw(https://svn.parrot.org/parrot/trunk parrot));
> -
> -chdir('parrot') || die
ore update.
diff --git a/build/gen_parrot.pl b/build/gen_parrot.pl
index 63173a3..572f474 100644
--- a/build/gen_parrot.pl
+++ b/build/gen_parrot.pl
@@ -43,12 +43,6 @@ close $REQ;
}
}
-print "Checking out Parrot r$reqsvn via svn...\n";
-system_or_die(qw(svn checkout -r), $reqs
In r38498, applied patch supplied by Michael Peters. See also:
https://trac.parrot.org/parrot/wiki/SmolderTaskList.
automatically pages).
>
> Perhaps a response to this thread is a little late, but I stumbled across
> git-svn today which allows interaction between git and a Subversion
> repository:
>
> http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
>
> I've not used i
s a little late, but I stumbled across
git-svn today which allows interaction between git and a Subversion
repository:
http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
I've not used it, so I can't speak to its effectiveness, but I thought of
this thread when I came across it. :)
Cory
- Original Message
> From: Patrick R. Michaud
> I will be making a decision (and possibly starting the
> migration) tomorrow. If anyone has any strong opinions
> one way or another, please let them be known quickly.
Hope I'm not too late to chime in.
Subversion's OK, but I would de
asily commit to the pugs subversion repository.
The existing mechanism (makefile calls svn to check out t/spec) will
work fine unmodified with rakudo in git.
...assuming that the system also has subversion installed and
readily available.
Sure, but we assume that now. :-)
To reg
On Tue, Jan 27, 2009 at 10:49 AM, Daniel Ruoso wrote:
> Em Ter, 2009-01-27 às 10:18 -0600, Patrick R. Michaud escreveu:
> > Well, we're now at the point where it's time to move the
> > Rakudo repository, and thus we need a decision on continuing
> > to use svn for
able to easily commit to the pugs subversion repository.
>
> The existing mechanism (makefile calls svn to check out t/spec) will
> work fine unmodified with rakudo in git.
...assuming that the system also has subversion installed and
readily available.
Pm
Moritz (>):
> I'm fine with both, and have no real preference atm, just a small bias
> towards git.
Same here. I like both systems, but ceteris paribus, I like git
better. I find it hard to tell in advance whether it'd be worth the
trouble switching, though.
// Carl
Patrick R. Michaud wrote:
> Switching the rakudo repository to git means that it would
> likely live on github, at least for a short time. We'd also
> have to provide mechanisms for people to continue to obtain
> and be able to easily commit to the pugs subversion repository.
>
> I will be making
Not long ago, Patrick R. Michaud proclaimed...
> Well, we're now at the point where it's time to move the
> Rakudo repository, and thus we need a decision on continuing
> to use svn for the repository or switching to git.
>
> Obviously staying with svn is very e
Em Ter, 2009-01-27 às 10:18 -0600, Patrick R. Michaud escreveu:
> Well, we're now at the point where it's time to move the
> Rakudo repository, and thus we need a decision on continuing
> to use svn for the repository or switching to git.
I think it primarily depends on how
scussions at this
> time -- there's been plenty of opportunity for that. Just state
> your preference and possibly a short statement of why you
> prefer that choice.
>
please, svn, so i can do svn switch --relocate and move on with my life.
~jerry
>
> time -- there's been plenty of opportunity for that. Just state
> your preference and possibly a short statement of why you
> prefer that choice.
>
I prefer git. It's fast and distributed and it would be nice to be able to
easily have local branches and whatnot. (I know SVK can do the last
Well, we're now at the point where it's time to move the
Rakudo repository, and thus we need a decision on continuing
to use svn for the repository or switching to git.
Obviously staying with svn is very easy to handle. The other
repositories that we have to coordinate with (parro
rot svn
revision 33960 ( and it seems some revisions before )
All perl6 tests are running successfully.
Cheers, and keep up the good work,
Jochen
On Wednesday December 10 2008 16:54, Jochen Plumeyer wrote:
> Hi folks,
>
> in the last days I tried several times with the respective late
# New Ticket Created by Jochen Plumeyer
# Please include the string: [perl #61278]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=61278 >
Hi folks,
in the last days I tried several times with the respective latest
to have its name/location changed soon.) If you need
> a pugs commit bit, please ask in #perl6 on irc.freenode.net.
...and the move is now done. The synopses currently live
in docs/Perl6/Spec/ of the pugs svn repository, but we may
be moving these to a different location in the repository
and/
We're in the beginning stages of deprecating smoke.parrotcode.org in
favor of our Smolder report system. So it would probably not be worth
our effort to modify the smoke system to accept smoke test reports from
new sources, such as proposed here for releases.
I would like to encourage you to try
One feature I'd
like to see: On the home page (http://smolder.plusthree.com/app/
public_projects/smoke_reports/8), could we squeeze in the SVN
revision number at which a report was generated -- perhaps flush
right on the same line as the "# Added ..." for each report.
We have
e tests nightly in the hopes that its useful, and
to
poke around with parrot as it evolves, so I think my estimation of the
svn rev
where it started hanging is accurate +/- 20 revs.
Krishna Sethuraman
[EMAIL PROTECTED]
Summary of my parrot 0.7.1 (r31839) configuration:
configdate='Thu O
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'
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 commits and patches arriving by email than to have to
go manually look t
Hi,
So before, this would not work out because it found the wrong outer:
--
.sub main
outer()
.end
.namespace [ 'Foo' ]
.sub outer
say "oops"
.end
.namespace []
.sub outer
$P0 = new 'Integer'
$P0 = 42
.lex '$a', $P0
test()
.end
.sub test :outer('outer')
$P0 = find_lex '$a'
On Sat Jun 21 17:49:51 2008, [EMAIL PROTECTED] wrote:
> Per #parrot:
>
> I'm trying to submit a smoke for parrot 0.6.3 on FreeBSD and
> I'm getting this error: * Sending data to smokeserver
> "http://smoke.parrotcode.org/smoke/
> "... error: The submitted smoke has an invalid format! Am I
>
nd
I'm getting this error: * Sending data to smokeserver
"http://smoke.parrotcode.org/smoke/
"... error: The submitted smoke has an invalid format! Am I
missing something, or did I do something incorrectly?
apeiron: usually that's b/c you did svn export, not svn
Learned that Coke had already opened a ticket for this; merged this one
into that.
# New Ticket Created by James Keenan
# Please include the string: [perl #56122]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56122 >
Forwarding to open RT:
Original Message
Subject: [PATCH] add git-
On Thu Jun 19 09:56:35 2008, coke wrote:
> Forwarding to parrotbug to open a ticket.
>
>
> -- Forwarded message --
> From: Hans Dieter Pearcey <[EMAIL PROTECTED]>
> Date: Wed, Jun 18, 2008 at 2:23 PM
> Subject: [PATCH] add git-svn instructions to gett
rom: Hans Dieter Pearcey <[EMAIL PROTECTED]>
Date: Wed, Jun 18, 2008 at 2:23 PM
Subject: [PATCH] add git-svn instructions to gettingstarted.pod
To: [EMAIL PROTECTED]
The obvious way to use git-svn with the parrot repo will result in the entire
history being checked out, which is undesira
The obvious way to use git-svn with the parrot repo will result in the entire
history being checked out, which is undesirable. The attached patch points
people towards only checking out HEAD.
hdp.
diff --git a/docs/gettingstarted.pod b/docs/gettingstarted.pod
index e6e18f8..731e434 100644
--- a
ndex: root.in
===
--- root.in (revision 28471)
+++ root.in (working copy)
@@ -163,11 +163,11 @@
# NOTE: eventually, we should remove --keep-exit-code and --fudge
# as the goal is that all tests must pass without fudge
spectest: all t/spec
- cd t/spec && svn up
+
Hi,
in r26841 I removed the directory 'compilers/past-pm', resolving the
deprecation item from RT#48030.
After updating to the new revision, a 'perl Configure.pl' is required,
as Makefile dependencies have changed.
Best regards,
Bernhard
Since I have not experienced this problem in > 1 month, and since it's
better dealt with by notifying Robert and having him track it in his RT
queue, I am going to cross my fingers and close this ticket.
Seems to work now, once I clean up my client side. (Had to do a little svn
cleanup and remove the old directory before it would go through, but now it
looks good.)
Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -Original Mess
I'm glad also! But If I had read this mail before reinstalled SVN
client, I would be glader. ;)
On Sun, Mar 30, 2008 at 10:12 PM, Andrew Whitworth
<[EMAIL PROTECTED]> wrote:
> Oh, i'm glad this is a bug in the repository, when it happened to me,
> I assumed that my SVN cl
>> This should be fixed in r26641.
>>
>> Could you confirm?
>> --
Checkout on Windows XP now works.
--
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com
Oh, i'm glad this is a bug in the repository, when it happened to me,
I assumed that my SVN client was broken. Now I dont need to go through
the effort of uninstalling my SVN client, installing a new one, and
checking out the entire repository again.
--Andrew Whitworth
On Sat, Mar 29, 2008
h 30, 2008 4:31 AM
> To: [EMAIL PROTECTED]
> Subject: [perl #52264] Bug: duplicate directory names in SVN
>
> On Sa. 29. Mär. 2008, 20:04:14, [EMAIL PROTECTED] wrote:
> > There appear to be two directories, languages/HQ9plus and
> languages/hq9plus,
> > which confli
# New Ticket Created by "Ted Neward"
# Please include the string: [perl #52264]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52264 >
There appear to be two directories, languages/HQ9plus and languages/hq9plus,
which confl
# New Ticket Created by Matt Kraai
# Please include the string: [perl #52022]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52022 >
Howdy,
I'm using git-svn and have made some local commits. When I ru
ward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -Original Message-
> From: James Keenan via RT [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 15, 2008 6:38 AM
> To: [EMAIL PROTECTED]
> Subject: [perl #51732] Parrot crash in
chromatic wrote:
On Monday 17 March 2008 14:29:19 Alberto Simões wrote:
I think this is not new to anyone, but as parrot 0.6.0 is preparing to
exit the cage, here is some information about running make test on
latest svn r26457.
Darwin 10.5.2:
Test Summary Report
---
t/src
On Monday 17 March 2008 14:29:19 Alberto Simões wrote:
> I think this is not new to anyone, but as parrot 0.6.0 is preparing to
> exit the cage, here is some information about running make test on
> latest svn r26457.
> Darwin 10.5.2:
>
> Test Summary Report
> ---
Hi
I think this is not new to anyone, but as parrot 0.6.0 is preparing to
exit the cage, here is some information about running make test on
latest svn r26457.
Linux 2.6.24, x86:
All tests successful.
Files=559, Tests=11128, 327 wallclock secs ( 5.32 usr 1.21 sys +
242.19 cusr 48.13
On Sat Mar 15 01:27:37 2008, [EMAIL PROTECTED] wrote:
> Sorry, you're right, the error did occur during the nmake part of the
>build; I just wanted to make it clear (in case it mattered) that
>ActiveState was used to run the Configure.pl script. Do you still
>need the complete make outp
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -Original Message-
> From: James Keenan via RT [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 3:15 PM
> To: [EMAIL PROTECTED]
> Subject: [perl #51732] Parrot crash in SVN tip
On Friday 14 March 2008 15:15:07 James Keenan via RT wrote:
> On Fri Mar 14 06:31:08 2008, [EMAIL PROTECTED] wrote:
> > ..\..\parrot.exe ..\..\compilers\tge\tgc.pir
> > --output=POST\Grammar_gen.p
> >
> > ir POST\Grammar.tg
> >
> > Parrot VM: PANIC: Null vtable used; did you add a new PMC
On Fri Mar 14 06:31:08 2008, [EMAIL PROTECTED] wrote:
> Visual Studio 2008, ActiveState Perl running configure.pl
>
>
>
> ..\..\parrot.exe ..\..\compilers\tge\tgc.pir
> --output=POST\Grammar_gen.p
>
> ir POST\Grammar.tg
>
> Parrot VM: PANIC: Null vtable used; did you add a new PMC?!
>
# New Ticket Created by "Ted Neward"
# Please include the string: [perl #51732]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=51732 >
Visual Studio 2008, ActiveState Perl running configure.pl
..\..\parrot.exe .
fferent
> >> linkage
> >
> > Excellent! A new Visual Studio version! Is this the free version or
> > a paid-for version. IIRC VS 2005 had some distinctions between the
> > two.
>
> FWIW, I used to build parrot from svn with VS 2008 express
> without any pro
ay.html?id=50956 >
src\oo.c(221) : error C2375: 'Parrot_oo_get_class' : redefinition; different
linkage
Excellent! A new Visual Studio version! Is this the free version or
a paid-for version. IIRC VS 2005 had some distinctions between the
two.
FWIW, I used to build parrot
.html?id=50956 >
>
>
> Steps look as follows:
>
>
>
>
>
> C:\Prg\parrot-svn>svn up
>
> At revision 25835.
>
>
>
> C:\Prg\parrot-svn>build_env.bat
>
> ActiveState Perl now on the PATH
>
> Setting environment for using Microsoft Visu
# New Ticket Created by "Joshua McAdams"
# Please include the string: [perl #50966]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50966 >
I'm using git-svn to check parrot; however, some of the parrot
# New Ticket Created by "Ted Neward"
# Please include the string: [perl #50956]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=50956 >
Steps look as follows:
C:\Prg\parrot-svn>svn up
At revision 2
m: Parrot via RT [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 18, 2008 1:46 AM
> To: [EMAIL PROTECTED]
> Subject: [perl #50956] AutoReply: Problems building in VS2008 with
> latest SVN tip
>
> Greetings,
>
> This message has been automatically generated in response to
Dear parroteers-
A small number of people have reported periodic issues committing to
the parrot subversion repository.
As of yet, we've been unable to create a repeatable test, find
anything obviously wrong that might be causing this issue, or even
logs that show a horrible error on our side.
ut I don't know what it is.
Whenever it happens, I just do an 'svn up' immediately after the
"failed" commit and everything seems to be okay.
Pm
James,
I've been seeing this problem off and on for over a month. As you've
noticed, it's rather intermittent, however, when the problem occurs it
persists for up to couple of hours. I've also seen that this is
platform independent, and so guessed that the problem existed at the
server end (mayb
On Sun Dec 30 10:01:18 2007, rgrjr wrote:
>
> Come to think of it, I did three commits each on Monday and Tuesday, and
> must have seen it then (either or both days).
>
> -- Bob
>
Perhaps not; the problem is intermittent. But yesterday I was getting
it o
From: "James Keenan via RT" <[EMAIL PROTECTED]>
Date: Sun, 30 Dec 2007 09:13:24 -0800
No, I first began to notice this two weeks ago. And the most frequent
occurrences were last night, when the maintenance on the server was
presumably complete.
Come to think of it, I did three com
On Sun Dec 30 09:04:25 2007, rgrjr wrote:
>
> Was that when the server was down a few days ago? Over the past few
> days, I have seen several examples of the "MERGE request failed ... 200
> OK" syndrome (which is particularly wierd) with Subversion client
> version 1.3.0. But I wouldn't swear t
Ticket/Display.html?id=49224 >
I am filing this ticket as a way of keeping track of some problems
with our infrastructure rather than with our code.
Over the last several weeks I have experienced intermittent, but
increasingly frequent, problems with commits to our SVN r
our infrastructure rather than with our code.
Over the last several weeks I have experienced intermittent, but
increasingly frequent, problems with commits to our SVN repository.
The nutshell description of this problem is:
1. I do 'svn commit'.
2. The commit appears to hang at "Tran
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
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
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
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, see
docs/dev/seatbelts.pod
for example, in r20546,
if you windows developers suddenly notice that your build output is
full of warnings, it's because we've increased the warnings level from
-W3 to -W4. since some level four warnings are so noisy, we've
disabled a few of them, until we get the others under control.
if you have msvc and an eye for f
On 18/07/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 7/17/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
> Initial comments (perhaps more to come):
>
> Run podchecker over the doc.
>
> Can you set your editor's line wrap settings such that when I say
> 'perldoc commiter_guide.pod', I don't ge
On 7/17/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
Initial comments (perhaps more to come):
Run podchecker over the doc.
Can you set your editor's line wrap settings such that when I say
'perldoc commiter_guide.pod', I don't get ugly wraps?
And now for a theological argument: Should i
Initial comments (perhaps more to come):
Run podchecker over the doc.
Can you set your editor's line wrap settings such that when I say
'perldoc commiter_guide.pod', I don't get ugly wraps?
And now for a theological argument: Should it be 'commiter' or 'committer'?
kid51
How does this file look? Does it explain everything which needs to be
explained? If everything's ok (or noone makes any noise over the next
few days) I'll add this file to docs/project.
Comments most definitely welcome.
Paul
commiter_guide.pod
Description: Binary data
On Fri Mar 23 11:37:34 2007, tewk wrote:
> tools/dev/mk_manifest_and_skip.pl should remove file from the MANIFEST
> that are scheduled to be svn deleted.
This problem should be corrected with revisions applied to trunk today
in r19893 (which applied to RT 43847 as well.
Both Coke and
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
Hi Paul!
I noticed you reindented the example when checking in the PDD07
change. Sorry to disagree with you, but this seems wrong to me.
Elsewhere in PDD07, it says: "neither PARROT_IN_CORE nor the outermost
_GUARD #ifdefs cause the level of indenting to increase." So I think
the indentation was
I have found a way to segfault parrot. (I know that the following code is
incorrect):
[EMAIL PROTECTED]/prg/parrot$ cat hello.pasm
main:
set I0, 3
set I1, 2
get_results "(0)", I0
set_args "(0,0)", P0, I1
fakesub:
get_params "(0,0)", I0, I1
add I0,
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
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
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
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
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.
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
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
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:
~ brings many things w
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
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
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
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
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
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
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
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 implement the interface
specified
led to be svn deleted.
Made a few more text edits in r17591. Paul Cochrane's changes approved,
ticket resolved.
e.
On Wed Feb 14 06:44:16 2007, ptc wrote:
> Documentation related to svn properties on files within Parrot needs
> to be cleaned up and reorganised. Namely put into the one place, and
> expanded upon. The current candidate for such a location is the
> coding standards pdd. Initial
1 - 100 of 219 matches
Mail list logo
