On Tuesday 15 July 2008, Brad Clements wrote:
> I tried some years back to integrate the CE changes into Python trunk.
> However there were too many changes spread all over the place. It was
> hard to get them reviewed.
I know of some projects (Boost, STLport) where the biggest batch of changes
was to fix assumptions (like TCHAR=char) or wrong uses of feature macros
(like checking _MSC_VER==1200 to determine whether a VC6-style compiler is in
use). These are often repeated all over the place, but can pretty well be
explained even to desktop-win32 people because even there they are slightly
incorrect, they only don't happen to break.
> Plus some things about CE were just too difficult to workaround,
> requiring lots of C macros that weren't not appealing to core developers:
>
> no concept of current directory
>
> non-writable errno
>
> non-standard floating point math handling.
- No environment variables.
- No *A function variants of the win32 API, only the *W ones.
- Very restricted C API to build on.
Just two questions here:
1. The non-writable errno, how does that matter? IIRC, it doesn't support
errno at all, so you must use the win32 SetLastError() and GetLastError().
And anyway, I would rather live with Python features unsupported than no
Python at all.
2. What do you mean with the floating point math handling? AFAIK, it still
strongly depends on the OS and target architecture, surely there are other
platforms that don't support
I can't fathom the impact of the necessary changes, which Python version were
you building your patches on? Are the patches still available somewhere? Can
you give me a link to the discussions?
Uli
--
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen,
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht
verantwortlich.
**************************************************************************************
_______________________________________________
PythonCE mailing list
PythonCE@python.org
http://mail.python.org/mailman/listinfo/pythonce
