On Thursday 25 September 2008, Martin v. Löwis wrote:
> > 1. TCHAR is always WCHAR
>
> Python shouldn't be using TCHAR at all; that getpathp uses it is
> misguided (IMO).
It already does, see below...
> > The first point is interesting to the desktop win32 variants because
> > everything since NT4 (or even 3.x) also used UCS2 or UTF-16 internally.
> > Only win9x and ME(?) use 8-bit chars, and since support for them is being
> > dropped, this would save a few conversions while allowing better Unicode
> > support. I think getting Python to compile with _UNICODE #defined will be
> > my first step.
>
> Please don't. Whether or not _UNICODE is defined should have no effect.
Well, currently it does make a difference. Simple example: CreateFile(). One
of the parameters is actually documented at LPCTSTR, which is a TCHAR string.
That means that under CE, CreateFile(), which is actually a macro, resolves
to CreateFileW and the existing code that passes a char-string doesn't work.
> > The third means that functions like e.g. system() are simply not
> > available in the supplied C API.
>
> In this case, not defining HAVE_SYSTEM would be already sufficient, no?
I'll take a look, I actually don't know.
> > The last one only affects the build system and possibly the integration
> > of unit testing. pythonce.sf.net already have one based on SCons, which
> > is nice and easily extended. Being able to build 64 bit variants on 32
> > bit systems and vice versa might be another benefit.
>
> Wouldn't it be easier to extend the VS projects? VS targets CE fairly
> well, no?
VS2005 works really good with CE5 and later. My problem here is that I can't
provide a projectfile that suits everyone, because different devices have
different SDKs and each configuration/SDK/CPU is another entry in that file.
Further, the SDKs or devices differ in what they support, the platform CE as
such doesn't exist.
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.
**************************************************************************************
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
