<html>#2686: Rename CCTK_REAL -> double when float is not tested
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Zach Etienne</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></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Erik Schnetter):</p>
<p>I’m not convinced they would break. I assume that many of them would switch to double precision for intermediate calculations, but they wouldn’t per se break. And if they break then it’s usually just a compile-time error that is straightforward to correct, such as e.g. calling <code>max(x, 1.0)</code> in C++.</p>
<p>In fact, I am going to propose that we should build the commonly used thorns with single precision and correct these compiler errors.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2686/rename-cctk_real-double-when-float-is-not'>https://bitbucket.org/einsteintoolkit/tickets/issues/2686/rename-cctk_real-double-when-float-is-not</a></p>
</html>