Neil Schemenauer wrote: > nnorwitz@users.sourceforge.net wrote: > >>Need to make sure that preprocessor directives start in first column. >>This means we can't indent code which has preprocessor directives, >>nor have a space between [ #include for example. > > What does the C standard say about this? I'm curious. No idea, but emacs mode is pretty clear on this: you don't get syntax highlighting when moving the # beyond column 1. What I usually do is to indent the directive after the #: #ifdef MX_BUILDING_MXDATETIME # define MXDATETIME_EXTERNALIZE MX_EXPORT #else # define MXDATETIME_EXTERNALIZE MX_IMPORT #endif -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Feb 24 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 36 days left EuroPython 2003, Charleroi, Belgium: 120 days left
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4