Python + Borland - msvcrt = grr.

[Stephen Hansen]

    Care to share? :) I just did a Google Groups search and couldn't find
anything from you on the subject. Just pointers to the instructions for
building extentions to Python, which is not what I want :) Ideally, I want
to be able to track the Python CVS and compile it with either VC or Borland,
depending on the phase of the moon.

    As for a -D_DEBUG problem; I have not hit any actual _problems_ besides
_winreg and its use of certain functions for dealing with wide chars in the
registry that Borland seems to be missing.

--Stephen
(replace 'NOSPAM' with 'seraph' to respond in email)

--
"jj" <jj at void.si> wrote in message
news:s1laet0bi12niusq4e51cnhm1n8eoeuc7d at 4ax.com...
> Hm, I posted the same stuff a month ago.
> I hope you fixed -D_DEBUG issue.
>
> JJ
> On Mon, 23 Apr 2001 07:06:02 GMT, "Stephen" <news at myNOSPAM.org> wrote:
>
> >Howdy,
> >
> >    I just sent in the patch to fix up all the Python sources to let it
> >compile from the Borland free compiler or C++Builder. This leaves two
issues
> >remaining before I put up the projects/makefiles somewhere:
> >
> >    #1) BCC is giving off the STRANGEST warnings. They make no
sense-at-all,
> >it seems to me that the compiler doesn't comprehend that a variable that
> >only gets modified by macros is actually being modified, so it complains
a
> >LOT about 'variable is assigned a value but never used' etc. Anyways, I'm
> >looking to the C++Builder for a fix on this :)
> >
> >    #2) 'msvcrt'. That's the only barrier to actually having the sources
> >compile if my patch is added in. I havn't yet actually looked at how much
> >can be salvaged/#ifdef'd around to duplicate the functionality for
> >borland... but I have a question:
> >
> >    Why the heck is it called _msvcrt_? Half of it will work right now --
I
> >know Borland supports putch/getch, for instance. The other half will
likely
> >just need some minor fixes. The module *really* should be called
> >'winconsole' or something.
> >
> >Anyways. :)
> >
> >--Stephen
> >(replace 'NOSPAM' with 'seraph' to respond in email)
> >
>