On Mon Dec 17 14:44:55 2007, jhorwitz wrote:
> t/op/copy.t passes with this patch. can others try it out?
>
Jeff's patch enabled me to build successfully on both Darwin and Linux
(the Debian box). I ran 'make test' on the Linux and all non-TODO tests
passed. So I have applied it to trunk in r2
On Mon, 17 Dec 2007, chromatic wrote:
Okay, so memcpy doesn't fix it. That's good to know. How about explicitly
putting the destination PMC in a named variable so there's less pointer
shuffling and macro madness?
memmove fixes it. i submitted a patch, but for some reason it hasn't made
it
apologies for the top post in my previous reply. didn't realize all that
error output was down there! :-P
Jeff Horwitz wrote:
unfortunately, chromatic's memcpy patch still generated the compiler
error, perhaps because gcc is optimizing it back to the original code
it was replacing.
using memmove fixes this issue. it performs the copy, but it's not
optimized in the same way because it deals with
unfortunately, chromatic's memcpy patch still generated the compiler
error, perhaps because gcc is optimizing it back to the original code it
was replacing.
using memmove fixes this issue. it performs the copy, but it's not
optimized in the same way because it deals with potentially overlappi
On Monday 17 December 2007 12:52:05 James Keenan via RT wrote:
> No, at least not on Ubuntu. (Will have to check later on other OSes.)
Okay, so memcpy doesn't fix it. That's good to know. How about explicitly
putting the destination PMC in a named variable so there's less pointer
shuffling a
On Dec 17, 2007, at 4:17 PM, Paul Johnson wrote:
Which is where, in C++, you would be using the mutable keyword. I
don't
think this has yet made it into any C standard, but my knowledge in
these areas is a little out of date.
No, you can't. Alas. I'm going to have to give up on the CONS
On Mon, Dec 17, 2007 at 09:50:32PM +, Nicholas Clark wrote:
> On Mon, Dec 17, 2007 at 10:06:42AM -0600, Andy Lester wrote:
> > Andy: My consting has run into its greatest challenge yet.
> > Andy: Making self args to PMCs consts where appropriate.
> > Andy:
> > Andy: INTVAL such_and_such_elemen
On Mon, Dec 17, 2007 at 10:06:42AM -0600, Andy Lester wrote:
> Andy: My consting has run into its greatest challenge yet.
> Andy: Making self args to PMCs consts where appropriate.
> Andy:
> Andy: INTVAL such_and_such_elements( PMC *self );
> Andy: Tell me that *self shouldn't be const.
> Andy: Go
No, at least not on Ubuntu. (Will have to check later on other OSes.)
Here's the last part of the 'make' output:
src/string.c
src/ops/core_ops.c
src/ops/debug.ops: In function ‘Parrot_debug_break’:
src/ops/debug.ops:103: warning: null argument where non-null required
(argument 2)
src/ops/debug.o
Author: petdance
Date: Mon Dec 17 11:25:23 2007
New Revision: 24013
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Log:
added note about checking strcmp() as a boolean
Modified: trunk/docs/pdds/pdd07_codingstd.pod
==
-
On Saturday 15 December 2007 15:11:54 James Keenan wrote:
> This afternoon I began to get failures in 'make'. Via IRC, pmichaud,
> jonathan and I tracked the break point down to r23917.
>
> At r23917, when I configure with 'perl Configure.pl' -- and no
> options -- I get the breakage described i
On Mon Dec 17 08:24:49 2007, doughera wrote:
> It passed all tests here. I haven't had time to review the actual patch,
> but the strategy you describe seems sound.
>
> However, I do want to worry about one thing: I worry about the growing
> time required to run all of these tests. Just runni
On Dec 17, 11:35 am, [EMAIL PROTECTED] (Paul Cochrane)
wrote:
> # New Ticket Created by Paul Cochrane
> # Please include the string: [perl #48749]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=48749>
>
> I'm currently gett
It would be most helpful if someone could setup a combust installation
on feather to facilitate updates to (and more importantly, development
on) the parrotcode website.
http://combust.develooper.com/
Thanks!
--
Will "Coke" Coleda
On Fri, 14 Dec 2007, James Keenan wrote:
> If at first you don't succeed ...
>
> The patch attached refactors config/inter/progs.pm for the purpose of
> increasing its testability.
It passed all tests here. I haven't had time to review the actual patch,
but the strategy you describe seems so
These problems were apparently fixed at some point over the last two
weeks, as I was able to 'make test' on Darwin last night and have all
tests pass (except, of course, the shootout). Closing ticket.
On Mon Dec 17 06:30:45 2007, particle wrote:
> >
> i see that as of r23980 (and beyond) you've moved these subs into a new
> module Parrot::Configure::Compiler, converted them to methods, and made
> the module a superclass of Parrot::Configure. this seems sane. carry on.
> ~jerry
Yes, I got it p
Andy: My consting has run into its greatest challenge yet.
Andy: Making self args to PMCs consts where appropriate.
Andy:
Andy: INTVAL such_and_such_elements( PMC *self );
Andy: Tell me that *self shouldn't be const.
Andy: Go on, tell me.
Andy: You can't.
particle: of course i can't
particle: in
On Sat Dec 15 15:11:53 2007, [EMAIL PROTECTED] wrote:
> This afternoon I began to get failures in 'make'. Via IRC, pmichaud,
> jonathan and I tracked the break point down to r23917.
>
Given that I originally reported this failure as occurring on a fairly
standard Debian installation (the only
On Sun Dec 16 10:31:58 2007, [EMAIL PROTECTED] wrote:
> James Keenan via RT wrote:
> > For no reason more profound than ease of editing, when I went to require
> > that each of 6 Parrot::Configure::Step methods be passed $conf
> > explicitly, I put that argument first.
> >
> > Which of course make
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Dec 17 14:00:03 2007 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
On Mon, Dec 17, 2007 at 10:24:25AM +0100, Paul Cochrane wrote:
> 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 le
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #48749]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=48749 >
I'm currently getting the following failure on Win32 (VisualStudio
2005, ActiveState Pe
Paul Cochrane wrote:
Unfortunately, I wish I could say the same. I'm getting the following error:
(Debian, gcc 4.1.2, r24008)
Configure with --cgoto=0 for now, and I'll ci a workaround in the code
later today. We'll revisit it to work out a Good Solution after the
release, but this breakage
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 getti
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.
-- c
27 matches
Mail list logo
