On 01/04/2008, Mark Glines via RT [EMAIL PROTECTED] wrote:
On Sat Mar 29 15:54:09 2008, [EMAIL PROTECTED] wrote:
I ran a fulltest with this patch applied, and everything's fine on x86
(where it matters).
Hi,
The root.in portion of this patch breaks non-i386, JIT capable
platforms.
Hallo Bernhard,
On 06/04/2008, Bernhard Schmalhofer via RT
[EMAIL PROTECTED] wrote:
On Di. 10. Jul. 2007, 07:15:27, ptc wrote:
In the file lib/Parrot/Test.pm there is the todo item:
# TODO: $language should be the name of the test Module
# that would
Jim,
Given Joshua's comments, should we still be considering this patch?
My guess is no. The compiler warning is probably gone by now anyway.
Paul
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote:
On Thu Jun 28 10:26:30 2007, ptc wrote:
Hi,
as part of my cleaning up the usage of 'INTERP', 'Interp' and
'interpreter' to consistently use 'interp', as well as changing
internal_exception()s to real_exceptions(), here are
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote:
Paul,
I see that you touched src/pmc/pair.pmc after your last post in this thread.
r22490 | paultcochrane | 2007-10-25 16:10:19 -0400 (Thu, 25 Oct 2007) |
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote:
On Thu Nov 08 08:25:28 2007, ptc wrote:
James,
Thanks for the report! I forgot to add parrot.h to the list of
includes. Could you add:
#include parrot/parrot.h
just before the other include statement in
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote:
Joshua, Paul:
Can you give us an update on the status of patch still?
As far as I remember, it still needs to be tested on the various runcores.
Paul
I just checked the properties in the repository for this file before
and after your commit, and they seem identical.
Yeah, that happened to me too but in my svn checkout. In the svk
checkout things seemed as though things weren't correct, so I
committed the changes.
If the test is failing
Patch applied in r25869. Closing ticket.
Patch applied in r25765. Closing ticket.
Andy's patch applied in r25763. This corrects the issue. Closing the
ticket.
Applied a modified version of the patch in r25767. Closing ticket.
On 07/02/2008, Ron Blaschke [EMAIL PROTECTED] wrote:
jerry gay wrote:
On Feb 7, 2008 5:38 AM, via RT Ted Neward
[EMAIL PROTECTED] wrote:
t/library/pg.
Interestingly, a parrot.exe process is left running, even after Ctrl-C'ing
the console window in
On 03/02/2008, via RT Bob Rogers [EMAIL PROTECTED] wrote:
# New Ticket Created by Bob Rogers
# Please include the string: [perl #50518]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=50518
I notice that
On 28/01/2008, James Keenan via RT [EMAIL PROTECTED] wrote:
On Sun Jan 27 17:14:11 2008, tiro wrote:
Could you try setting MACOSX_DEPLOYMENT_TARGET to 10.4 to see if that
fixes the problem?
Okay, I figured out how to do that ... but no better results.
[parrot] 566 $
On 23/01/2008, Allison Randal via RT [EMAIL PROTECTED] wrote:
On Tue Jan 22 15:38:11 2008, [EMAIL PROTECTED] wrote:
Are you building a static or a shared binary? Did this problem only
show up after Coke switched the default to shared?
Shared. I don't know the exact timing of the change
On 22/01/2008, chromatic [EMAIL PROTECTED] wrote:
On Monday 21 January 2008 08:58:25 Paul Cochrane wrote:
when building parrot on Solaris I get most of the way through the
build, but right at the end, building pbc_to_exe fails with the
following output:
It seems that the Makefile macro
On Tue Dec 04 20:12:24 2007, coke wrote:
From PDD17:
=item class_type
INTVAL class_type(INTERP, PMC* self)
Return the integer type of the PMC. [NOTE: will be deprecated when type
IDs are deprecated.]
The attached patch removes this vtable entry. The only thing still
which seems to
On Sat Jan 12 04:42:26 2008, allison wrote:
This opcode has been superseded by 'inspect'.
The pmcinfo opcode is removed by the attached patch. I would have
committed this directly however, I'm not 100% sure that removing the:
'Class PMCs also have the I am a class flag set on them.'
test was
Completed as per r25053.
Alan,
The attached patch should quieten some of the grumbling. It's entirely
comments, so should not have any functional impact.
The patch wasn't attached. Could you try again?
Thanks,
Paul
On 15/01/2008, Matisse Enzer [EMAIL PROTECTED] wrote:
On Jan 14, 2008, at 1:00 AM, Paul Cochrane wrote:
Matisse,
this is great work! Would it be possible for you to summarise this on
the parrot wiki somewhere?[1] Then we have a more permanent and
central location for the information
Matisse,
this is great work! Would it be possible for you to summarise this on
the parrot wiki somewhere?[1] Then we have a more permanent and
central location for the information.
Paul
[1] http://www.perlfoundation.org/parrot/index.cgi?parrot
Both passing and failing builds from buildbot
James,
However, based on my experience and ptc's in cage-cleaning, I'd
recommend opening up individual RTs for test files that would benefit
subdividing. That way, we can more easily identify which test files
have been refactored and which remain to be done.
Given the way we currently seem
On 09/01/2008, chromatic [EMAIL PROTECTED] wrote:
On Monday 07 January 2008 20:09:26 Jarkko Hietaniemi wrote:
--- config/auto/warnings.pm.dist 2008-01-08 05:51:42.0 +0200
+++ config/auto/warnings.pm 2008-01-08 06:01:23.0 +0200
@@ -132,17 +132,22 @@
$verbose =
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
On 31/12/2007, James E Keenan [EMAIL PROTECTED] wrote:
Andy Armstrong wrote:
Sorry if I've missed something recent that means that this is expected
behaviour but r24318 is hanging during make test on Mac OS 10.5.1 / Intel.
The test log and pictures of the process probe are here:
On 26/12/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
Once I got the tuits, the merging of these two Parrot configuration
steps went quite quickly. But before applying a patch to trunk, I would
like the assistance of other testers on the 4 CPU platforms handled by
gen::cpu and what
On 20/12/2007, James E Keenan [EMAIL PROTECTED] wrote:
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
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
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)
# Exited with error
Hi,
I've been doing some testing on Win32 as well, here are my current
results: (I'm also still getting the failure I posted earlier with
t/examples/tutorial.t, so I've left it out)
Paul
System: WindowsXP
cc: Visual Studio 2005
perl: ActiveState
Parrot revision: 24034
On 17/12/2007, chromatic [EMAIL PROTECTED] wrote:
After fixing a few small tests, fulltest passes everything but a couple of
in-progress coding standards tests on my platform. The release is ready on
the world's most lenient platform.
Unfortunately, I wish I could say the same. I'm getting
the .pod files from the source, imho. (does parrot have a make docs
target?)
Yes, it's the make html target.
Paul
On 12/12/2007, jerry gay [EMAIL PROTECTED] wrote:
On Dec 11, 2007 11:08 PM, Andy Lester [EMAIL PROTECTED] wrote:
I made it make comment blocks look like this:
/*
=item CQUEUE_ENTRY * pop_entry
Does a synchronized removal of the head entry off the queue and
returns it.
On 07/12/2007, Allison Randal [EMAIL PROTECTED] wrote:
Andy Dougherty wrote:
Whether this is a defect in the vtables_4 test sourcefile for failing to
initialize the vtables, or whether pmc_new ought to be more defensive, I
can't say.
Looks like a bug in the test, as there are other
Apologies for the extra email! This was an abortive attempt to Ctrl-C
out of a command line RT session. Closing ticket.
On 02/12/2007, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Sun, Dec 02, 2007 at 10:44:08AM +0100, Paul Cochrane wrote:
... and I only
needed to switch off the warnings about a lack of Cuse
strict/warnings. At present, this isn't a maintanence burden, but as
soon as we get lots of nqp
On 01/12/2007, Will Coleda [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
Author: paultcochrane
Date: Sat Dec 1 06:08:08 2007
New Revision: 23307
Modified:
trunk/examples/sdl/blue_rect.pl
Log:
[examples]
- corrected editor coda
- added no critic flags to switch
Hi Jerry,
Besides the obvious _Perl6 and Parrot Essentials_, are there any
other books that one could use to get a good background for Parrot
development? I'm wondering if there are any references that people
developing Parrot are using.
AFAIK Perl6 and Parrot Essentials isn't very up to
https://rt.perl.org/rt3/Ticket/Display.html?id=46539
[BUG] compilers/pirc/new/pir.l failing t/codingstd/cppcomments.t
Coke commented on this on Oct 21, but ticket has not been resolved.
Spot check of smoke tests suggests it may now be passing on all OSes.
compilers/pirc/new/pir.l is exempt
On 28/11/2007, Patrick R. Michaud via RT
[EMAIL PROTECTED] wrote:
The attached coretest.patch file adds a make coretest target to
Parrot. This target runs a smaller subset of tests than the normal
make test target. On my system, make test completes in ~290
seconds, while make coretest
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 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 22/11/2007, chromatic [EMAIL PROTECTED] wrote:
On Wednesday 21 November 2007 12:50:48 [EMAIL PROTECTED] wrote:
Log:
[core,config] Moved executable code out of gcc_x86.h. This closes
RT#47245.
Does t/src/atomic.t still work for you after this change? It fails for me,
because the
On 18/11/2007, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Sun, Nov 18, 2007 at 06:03:28AM -0800, [EMAIL PROTECTED] wrote:
Log:
[codingstd] If a comma is followed by a single quote, it very likely in a
situation like: moo = ','; In which case, there shouldn't be a space
after the
On 17/11/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: chromatic
Date: Sat Nov 17 14:06:29 2007
New Revision: 22864
Modified:
trunk/src/pmc/closure.pmc
trunk/src/pmc/key.pmc
trunk/src/pmc/object.pmc
trunk/src/pmc/slice.pmc
trunk/src/pmc/timer.pmc
Log:
[PMC]
On 17/11/2007, James E Keenan [EMAIL PROTECTED] wrote:
Paul Cochrane wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #47523]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47523
Andy,
Here are the warnings I got on my latest run, along with the number of
times each one appeared: (this was with gcc-4.1.0 on Solaris/SPARC)
snip warnings summary
This is very helpful for me to try and improve the situtation.
Thanks! I'll switch off the visibility attribute warning if
On 13/11/2007, Nicholas Clark [EMAIL PROTECTED] wrote:
On Mon, Nov 12, 2007 at 12:33:41PM -0800, Andy Dougherty wrote:
It may well be there's an issue with gcc's optimizer, since the problem
goes away without optimization, but I think it's also fair to say that
the definition of
On 14/11/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: chromatic
Date: Tue Nov 13 17:42:13 2007
New Revision: 22824
Modified:
trunk/lib/Parrot/Configure/Step.pm
Log:
[configure] Don't use the libs in the configuration object when linking C
files
in the configuration
On 14/11/2007, Patrick R. Michaud [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 09:20:40AM -0500, Andy Dougherty wrote:
On Tue, 13 Nov 2007, Nicholas Clark via RT wrote:
On Mon, Nov 12, 2007 at 12:33:41PM -0800, Andy Dougherty wrote:
It may well be there's an issue with gcc's
On Sun Nov 11 09:57:07 2007, coke wrote:
On Mon Oct 22 15:02:26 2007, rgrjr wrote:
From: Paul Cochrane (via RT) [EMAIL PROTECTED]
Date: Mon, 22 Oct 2007 10:43:32 -0700
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46697]
# in the subject
kid51,
this error is caused by gcc_pcc.h using 'inline' directly, and I added
-std=c89 to the list of gcc compiler options just recently. What you
need to do is replace the 'inline' keyword in gcc_pcc.h with
PARROT_INLINE and everything should work again.
Paul
On 11/11/2007, via RT James
On 12/11/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
On Sun Nov 11 10:27:32 2007, ptc wrote:
kid51,
this error is caused by gcc_pcc.h using 'inline' directly, and I added
-std=c89 to the list of gcc compiler options just recently. What you
need to do is replace the 'inline'
On 10/11/2007, chromatic [EMAIL PROTECTED] wrote:
On Friday 09 November 2007 09:00:00 [EMAIL PROTECTED] wrote:
Author: paultcochrane
Date: Fri Nov 9 08:59:59 2007
New Revision: 22780
Modified:
trunk/src/objects.c
trunk/src/pmc/namespace.pmc
trunk/src/pmc_freeze.c
On 09/11/2007, Joshua Isom [EMAIL PROTECTED] wrote:
Did you test the exec runcore? I don't think any of that code is used
outside of the exec runcore so you aren't actually testing that code.
I'll have a go at testing against the exec runcore and see what turns
up. This is likely something we
James,
Thanks for the report! I forgot to add parrot.h to the list of
includes. Could you add:
#include parrot/parrot.h
just before the other include statement in gcc_pcc.c and see if things
make (after realclean) nicely for you?
Ta!
Paul
Failed on Darwin PPC at about 40% of the way thru
On 08/11/2007, chromatic [EMAIL PROTECTED] wrote:
On Wednesday 07 November 2007 14:58:40 Paul Cochrane wrote:
The file include/atomic/gcc_x86.h contains executable code. The
attached patch moves this code out into a new file
src/atomic/gcc_x86.c. make test passes, so things look ok
kid51,
On 05/11/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
The patch attached refactors configuration step auto::ctags to maximize
testability. It also provides 3 test files to replace ptc's original
test file. ptc's original functionality is, however, maintained intact.
Assuming
On 31/10/2007, Klaas-Jan Stol [EMAIL PROTECTED] wrote:
On Oct 31, 2007 4:35 AM, chromatic [EMAIL PROTECTED] wrote:
On Tuesday 30 October 2007 19:27:52 James Keenan wrote:
As has been the case lately, a couple of 'pirc'-related files have
been failing metadata and coding standards tests.
On 31/10/2007, Klaas-Jan Stol [EMAIL PROTECTED] wrote:
sorry, it should have read r22631.
On Oct 31, 2007 11:33 AM, Klaas-Jan Stol [EMAIL PROTECTED] wrote:
Is it ok to revert r22361 now (where chromatic removed the linelength
test from the set of default run tests)?
If the tests are
This email didn't make the list so I'm sending it again.
Paul
-- Forwarded message --
From: Paul Cochrane [EMAIL PROTECTED]
Date: 29 Oct 2007 15:36
Subject: Re: [svn:parrot] r22585 - trunk/src
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
On 29/10/2007, [EMAIL
On 30/10/2007, jerry gay [EMAIL PROTECTED] wrote:
On Oct 30, 2007 1:58 PM, Paul Cochrane [EMAIL PROTECTED] wrote:
Modified: trunk/src/inter_create.c
==
--- trunk/src/inter_create.c(original)
+++ trunk/src
On Thu Mar 15 19:42:17 2007, ptc wrote:
Andy has a pretty decent set of rules for perl5's code in that
project's Makefile. Take a look at those for a start.
Andy Lester put a large chunk of effort into the options for both Sun
lint and BSD lint. After adding some extra flags to BSD lint
On 29/10/2007, Joshua Juran [EMAIL PROTECTED] wrote:
On Oct 28, 2007, at 8:28 AM, Klaas-Jan Stol wrote:
hi, when building parrot it reported a warning about some variable
string
in string.c
When checking out, I saw this:
static const char *
nonnull_encoding_name(STRING *s)
{
On Sun Oct 21 13:25:50 2007, ptc wrote:
On Thu Mar 15 19:12:48 2007, ptc wrote:
splint spews many many errors by default. Take a look at the
Makefile that perl5 has for the start of some rules that Andy worked
on for the perl5 code.
Andy Lester has done a very large amount of work on
On Tue Oct 02 13:39:30 2007, [EMAIL PROTECTED] wrote:
Parrot is no longer licensed under the GPL directly (though it is
available under the GPL through the Artistic 2.0). Update or remove
references to the GPL license in these files:
debian/copyright:45
Removed mention of some
On 27/10/2007, chromatic [EMAIL PROTECTED] wrote:
On Friday 26 October 2007 15:03:12 Paul Cochrane wrote:
The attached patch adds dependencies to lib/Parrot/Pmc2c/PCCMETHOD.pm
if the .pmc uses PCCMETHODs. This should also then allow the
t/codingstd/pccmethod_deps.t test to pass.
+1
On 25/10/2007, Allison Randal [EMAIL PROTECTED] wrote:
Paul Cochrane wrote:
I updated the subject of this ticket to substitute PMC with * as this
issue occurs more often than I first guessed (the problems one has
when going through code serially...). This issue is actually more
general
On 24/10/2007, via RT Paul Cochrane [EMAIL PROTECTED] wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46823]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46823
In t/pmc
On 23/10/2007, via RT James Keenan [EMAIL PROTECTED] wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #46727]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=46727
auto::ctags was
On 23/10/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
Am reopening this ticket to pose this question, which I also posed in RT
44171: Why $/ where a newline would suffice:
./config//init/optimize.pm:41:print $/ if $verbose;
Again, idiom copied from attributes.pm... If it's not
On 23/10/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
While examining this file for the purpose of writing tests, I noticed
that it uses Perl's special variable $/ in 6 instances where a newline
would suffice.
[parrot] 504 $ grep -n '$/' config/auto/attributes.pm
54:print $/ if
On 21/10/2007, Joshua Isom [EMAIL PROTECTED] wrote:
On Oct 20, 2007, at 2:33 PM, Paul Cochrane via RT wrote:
The ctags program is now detected at configuration time (this program
sometimes has different names on different systems) and now 'make tags'
should work out of the box for all
Patch applied in r22363. Thanks!
On Mon Mar 19 09:54:26 2007, ptc wrote:
On Sat Mar 17 14:19:51 2007, ptc wrote:
The lcov tool from the Linux Test Project
(http://ltp.sourceforge.net/coverage/lcov.readme.php) can be used to
produce html output of code coverage information (I believe this
looks
similar to Devel::Cover's
On Thu Mar 15 19:12:48 2007, ptc wrote:
splint spews many many errors by default. Take a look at the
Makefile that perl5 has for the start of some rules that Andy worked
on for the perl5 code.
Andy Lester has done a very large amount of work on this, and a very
good set of rules for splint
The only files which still have this issue outstanding are[1]:
src/jit/ppc/jit_emit.h
src/jit/alpha/jit_emit.h
src/jit/hppa/jit_emit.h
src/jit/mips/jit_emit.h
src/jit/sun4/jit_emit.h
Attached are patches for these files as I am unable to test on these
platforms (diff-ed agains
On Tue Jul 10 05:08:19 2007, ptc wrote:
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
On 15/10/2007, James E Keenan [EMAIL PROTECTED] wrote:
Paul Cochrane via RT wrote:
On Sun Jul 08 15:09:19 2007, ptc wrote:
At present we have to specify warnings flags for each version of gcc
(see config/auto/gcc.pm). This is a pain. Perl 5 is able to work out
automatically the warnings
4. Can you answer the question I posed in my July 8 response to your
original post?
I can't find anything relevant on July the 8th, although there was an
email on Sep the 8th... Is there a ticket number or another pointer
you can give me?
Thanks!
Paul
Hi all,
there is now a test in t/codingstds called filenames.t which
encapsulates the discussion here. Is this sufficient to now close
this ticket and to remove the old check_source_standards.pl program?
Paul
http://rt.perl.org/rt3/Ticket/Display.html?id=39824
Since the above ticket has now been resolved, does this mean that this
ticket can also be resolved?
Paul
James,
Thanks for pointing out what you meant. I think I must have been
having a bit of a brain-fade moment or something...
On Sun Jul 08 18:06:03 2007, [EMAIL PROTECTED] wrote:
Paul Cochrane wrote:
Perl 5 is able to work out
automatically the warnings flags of gcc and then use those
Oops, I forgot to attach the test...
On 16/10/2007, Paul Cochrane [EMAIL PROTECTED] wrote:
On 15/10/2007, Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
Paul Cochrane via RT schrieb:
On Fri Nov 17 14:17:18 2006, particle wrote:
~ all but one test have been adapted for and moved to t
On 16/10/2007, jerry gay [EMAIL PROTECTED] wrote:
On 10/16/07, Paul Cochrane [EMAIL PROTECTED] wrote:
On 15/10/2007, Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
Paul Cochrane via RT schrieb:
On Fri Nov 17 14:17:18 2006, particle wrote:
~ all but one test have been adapted
On Sun Jul 08 15:09:19 2007, ptc wrote:
At present we have to specify warnings flags for each version of gcc
(see config/auto/gcc.pm). This is a pain. Perl 5 is able to work out
automatically the warnings flags of gcc and then use those for
compilation. Parrot should do this too.
Automatic
On Fri Nov 17 14:17:18 2006, particle wrote:
~ all but one test have been adapted for and moved to t/codingstd/
~ remaining test is for not-yet-approved codingstd item
The remaining test complains about more than one '.' in a filename and
filenames which don't conform to the 8.3 format. My
On Sat Jul 15 14:47:48 2006, rblasch wrote:
Jerry Gay (via RT) wrote:
# New Ticket Created by Jerry Gay
# Please include the string: [perl #39760]
# in the subject line of all future correspondence about this
issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=39760
On Mon Oct 08 12:14:07 2007, leo wrote:
Am Montag, 8. Oktober 2007 19:05 schrieb Paul Cochrane:
So, the patch is right (however, for my wrong reasoning)? Is
everyone
happy if I apply it then?
$ svn ann src/pmc/pair.pmc
8374leo A Pair PMC represents one key = value mapping like
On 09/10/2007, Leopold Toetsch [EMAIL PROTECTED] wrote:
Am Dienstag, 9. Oktober 2007 22:25 schrieb Paul Cochrane:
In compilers/imcc/optimizer.c:move_ins_out() there is the todo item:
I really appreciate all the effort to todo-ize these items. But it shouldn't
be done too mechanically
On 10/10/2007, James Keenan via RT [EMAIL PROTECTED] wrote:
On Tue Oct 09 23:36:40 2007, ptc wrote:
Hi,
This patch fixes t/codingstd/c_parens.t failures on darwin (which I
don't have access to, hence the patch).
Files affected:
config/gen/platform/darwin/dl.c
On 08/10/2007, Joshua Juran [EMAIL PROTECTED] wrote:
On Oct 7, 2007, at 12:43 PM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #46223]
# in the subject line of all future correspondence about this issue.
# URL: http
On 08/10/2007, Joshua Juran [EMAIL PROTECTED] wrote:
On Oct 8, 2007, at 4:36 AM, Paul Cochrane wrote:
On 08/10/2007, Joshua Juran [EMAIL PROTECTED] wrote:
On Oct 7, 2007, at 12:43 PM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string
On 05/10/2007, chromatic [EMAIL PROTECTED] wrote:
On Thursday 04 October 2007 23:10:14 [EMAIL PROTECTED] wrote:
Modified:
trunk/src/pmc/parrotio.pmc
Log:
[pmc] An input argument to the open() method was freed just before it was
used. Thanks to Coverity (CID 131) for pointing this
Sorry for the extra email in everyone's inbox. I was trying to use
the rt command line tool but stuffed up.
Paul
On 01/10/2007, via RT Paul Cochrane [EMAIL PROTECTED] wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #45905]
# in the subject line of all future
This time I'm going to add some text to the ticket...
For the umteenth time...
src/exceptions.c has a todo comment in it:
* XXX TODO get rid of all the internal_exceptions or call them
* with an interpreter arg
The fact that we can't completely get rid of internal_exception() has
On Mon Oct 01 14:36:55 2007, ptc wrote:
In src/exceptions.c there is mention about exception being still in
TODO.
This means that something about exceptions is not yet finished, and
needs
to be implemented so that the code mentioned here (near
rethrow_c_exception()) can be completed. So,
Andy,
Just a following followup - I looked ath changes in rev 21619 and noticed
that the troublesome warning flags are still in the cage settings for
the default. Should they be moved to a v3.4 section also for the cage
cleaners?
I don't think it's worth it atm (unless you want to join the
1 - 100 of 426 matches
Mail list logo
