This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | skrah |
|---|---|
| Recipients | Amaury.Forgeot.d'Arc, Arfrever, Jim.Jewett, Ramchandra Apte, amaury.forgeotdarc, benjamin.peterson, casevh, ced, eric.smith, eric.snow, jjconti, lemburg, mark.dickinson, pitrou, rhettinger, skrah, vstinner |
| Date | 2012年03月11日.11:05:19 |
| SpamBayes Score | 0.00045422046 |
| Marked as misclassified | No |
| Message-id | <20120311110519.GA32380@sleipnir.bytereef.org> |
| In-reply-to | <1331093383.53.0.464429203652.issue7652@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Benjamin Peterson <report@bugs.python.org> wrote: > Speaking of inline, the "inline" keyword will have to go because it's not C89. Actually the trickier instances of "inline" in the .c files are already suppressed when LEGACY_COMPILER (i.e. C89) is defined. I've now listed the machine options here: http://hg.python.org/features/cdecimal/file/0f032cda94aa/Modules/_decimal/README.txt As I now remember, that was in fact necessary for CompCert. The "static inline" instances in header files might not be a problem even for embedded compilers, see e.g.: http://embeddedgurus.com/barr-code/2011/03/do-inline-function-bodies-belong-in-c-header-files/ IIRC also the Linux kernel uses "static inline" in header files. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年03月11日 11:05:21 | skrah | set | recipients: + skrah, lemburg, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, vstinner, casevh, eric.smith, benjamin.peterson, jjconti, Arfrever, ced, Amaury.Forgeot.d'Arc, eric.snow, Ramchandra Apte, Jim.Jewett |
| 2012年03月11日 11:05:20 | skrah | link | issue7652 messages |
| 2012年03月11日 11:05:19 | skrah | create | |