[Python-Dev] Split unicodeobject.c into subfiles (original) (raw)
Amaury Forgeot d'Arc amauryfa at gmail.com
Tue Oct 23 14:03:44 CEST 2012
- Previous message: [Python-Dev] Split unicodeobject.c into subfiles
- Next message: [Python-Dev] Split unicodeobject.c into subfiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2012/10/23 Antoine Pitrou <solipsis at pitrou.net>:
I agree with Marc-André, there's no point in compiling those files separately. #include'ing them in the master unicodeobject.c file is fine.
I also find the unicodeobject.c difficult to navigate. Even if we don't split the file, I'd advocate a better presentation of its content.
Could we have at least clear sections, with titles and descriptions? And use the ^L page separator for Emacs users?
Code in posixmodule.c could also benefit of a better layout.
-- Amaury Forgeot d'Arc
- Previous message: [Python-Dev] Split unicodeobject.c into subfiles
- Next message: [Python-Dev] Split unicodeobject.c into subfiles
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]