<html>#2566: check for -traditional in FPP's behaviour
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td></td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Cactus passes Fortran code (at least with extensions .F77 .F and .F90) through the C preprocessor in FPP passing FPPFLAGS.</p>
<p>This cpp must use traditional (pre-ANSI) behaviour, ie be string and not token based to preserve whitespace in Fortran fixed format code and handle concatenation using <code>FOO/**/BAR</code> correctly.</p>
<p>Getting this wrong by setting eg only FPP in an option list results in strange error messages. </p>
<p>Cactus' configure should check that FPP and FPPFLAGS behave as expected. Eg by processing:</p>
<div class="codehilite"><pre><span></span><span>TRAD/**/ITIONAL</span>
</pre></div>
<p>which produces:</p>
<div class="codehilite"><pre><span></span><span>TRADITIONAL</span>
</pre></div>
<p>with <code>--traditional</code> and</p>
<div class="codehilite"><pre><span></span><span>TRAD ITIONAL</span>
</pre></div>
<p>without, so one can <code>grep</code> for the expected string.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2566/check-for-traditional-in-fpps-behaviour'>https://bitbucket.org/einsteintoolkit/tickets/issues/2566/check-for-traditional-in-fpps-behaviour</a></p>
</html>