#2566: check for -traditional in FPP's behaviour
| Reporter: | |
| Status: | wontfix |
| Milestone: | |
| Version: | development version |
| Type: | enhancement |
| Priority: | major |
| Component: |
Changes (by Roland Haas):
| status: | wontfix (was new) |
Comment (by Roland Haas):
Actually Cactus itself contains such a check in src/include/cctk_Types.h:
/* Determine whether we have a traditional or an ANSI cpp. */ #ifdef FCODE /* The empty comment in the definition of CCTK_ANSI_FPP will either turn into nothing or into white space. There must not be any add spaces around this empty comment. A traditional cpp will turn it into nothing, an ANSI cpp will turn it into white space. Depending on this, CCTK_ANSI_FPP will either turn into a single separate token (which lead to the value 0), or into two separate tokens (which lead to the value 1). This is magic. */ #define CCTKi_FPP_A #define CCTKi_FPP_B 1 #define CCTKi_FPP_ACCTKi_FPP_B 0 #define CCTK_ANSI_FPP CCTKi_FPP_A/**/CCTKi_FPP_B #endif
so really it should support both. Namely if code fails if FPP is not traditional then that could should be changed so that it works both with and without traditional.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2566/check-for-traditional-in-fpps-behaviour