[Python-Dev] Re: python/dist/src/Objectsunicodeobject.c, 2.204, 2.205 (original) (raw)
Nick Coghlan ncoghlan at iinet.net.au
Sat Dec 20 04:09:48 EST 2003
- Previous message: [Python-Dev] Re: python/dist/src/Objectsunicodeobject.c, 2.204, 2.205
- Next message: [Python-Dev] Re: [Python-checkins] python/dist/src/Objects unicodeobject.c, 2.204, 2.205
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Peters wrote:
[Hye-Shik Chang]
BTW, do we really support architectures with 9bits-sized char? [...] Skip's idea of making config smarter about this is a good one, but instead of trying to "fix stuff" for a case that's probably never going to arise, and that can't really be tested anyway until it does, I'd add a block like this everywhere we know we're relying on 8-bit char: #ifdef HASFUNNYSIZECHAR #error "The following code needs rework when a char isn't 8 bits" #endif /* A comment explaining why the following code needs rework * when a char isn't 8 bits. */
This would probably be appropriate for those TI DSP's I mentioned. While they genuinely have a 16-bit char type, they're also intended for use as co-processors, rather than as the main controller for an application. That is, a more standard CPU should be used to handle the general application programming, while the DSP is used for the serious number crunching (that's what it is made for, after all).
Anyone who thinks they want to run Python on the DSP core almost certainly needs to have a long hard think about their system design.
Cheers, Nick.
-- Nick Coghlan | Brisbane, Australia Email: ncoghlan at email.com | Mobile: +61 409 573 268
- Previous message: [Python-Dev] Re: python/dist/src/Objectsunicodeobject.c, 2.204, 2.205
- Next message: [Python-Dev] Re: [Python-checkins] python/dist/src/Objects unicodeobject.c, 2.204, 2.205
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]