[EMAIL PROTECTED] wrote:
> Jeremy> Looks good to me. Why don't you check it in.
>
> I did, but it broke the C build, so I reverted it and reopened the patch.
> I'll try to take a look at it more later today.
I took a different approach, introducing a second kind of sequence.
Since most acces
> "Jeremy" == Jeremy Hylton <[EMAIL PROTECTED]> writes:
Jeremy> Looks good to me. Why don't you check it in.
I did, but it broke the C build, so I reverted it and reopened the patch.
I'll try to take a look at it more later today.
Skip
___
Pyt
Looks good to me. Why don't you check it in.
Jeremy
On 4/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Jeremy> The code in compile.c is pretty dodgy. I'd like to think of a
> Jeremy> better way to represent an array of cmpop_ty objects than
> Jeremy> casting ints to void*
Jeremy> The code in compile.c is pretty dodgy. I'd like to think of a
Jeremy> better way to represent an array of cmpop_ty objects than
Jeremy> casting ints to void* and then back.
http://python.org/sf/1469594
might be a step in the right direction.
I assigned it to Anthony. Feel
So I lied - I found the time today to spread the magic pixie dust of
extern "C" {} around to get the Python core to build and link with
g++. (It still builds with gcc). There's still an issue with
Modules/_sre.c, and now that we can run setup.py, there's lots and
lots of errors from the various
On Thursday 13 April 2006 12:03, Jeremy Hylton wrote:
> The code in compile.c is pretty dodgy. I'd like to think of a
> better way to represent an array of cmpop_ty objects than casting
> ints to void* and then back.
Well, it's compiling and working with C++ now, at least. But yeah,
that's prett
On 4/12/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> The code is _nearly_ building fine. there's an issue in _sre.c with
> some code that either returns a Py_UNICODE* or an SRE_CHAR* (unsigned
> char*) in a void*. The code probably needs a refactoring to deal with
> that. There's also
> Python/c
On Thursday 13 April 2006 10:59, Skip Montanaro wrote:
> > > Anthony> I've done a lot of the work to get Python to build
> > > with g++ -
> > >
> > > Is this on a branch or available as a patch somewhere?
> >
> > It's the trunk.
>
> Is there a primer that will get me to where Anthony is? I tri
> > Anthony> I've done a lot of the work to get Python to build with g++ -
> > Is this on a branch or available as a patch somewhere?
>
> It's the trunk.
Is there a primer that will get me to where Anthony is? I tried the obvious
CC=g++ ./configure --with-cxx=g++
and the build fails t
[EMAIL PROTECTED] wrote:
> Anthony> I've done a lot of the work to get Python to build with g++ -
> Anthony> ... I can't spend much more time on this now, but if someone
> Anthony> wants to take over and finish it off, that'd be great.
>
> Is this on a branch or available as a patch so
Anthony> I've done a lot of the work to get Python to build with g++ -
Anthony> ... I can't spend much more time on this now, but if someone
Anthony> wants to take over and finish it off, that'd be great.
Is this on a branch or available as a patch somewhere?
Skip
___
11 matches
Mail list logo
