<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 14, 2013 at 6:21 AM, Juhász Ádám <span dir="ltr"><<a href="mailto:jadaml@gmail.com" target="_blank">jadaml@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But cpp still a C pre-compiler and we all can agree,
that it is needed for MacPorts, otherwise neither cc nor c++ would work
properly, right?</blockquote></div><br>It is included in both gcc and clang, and also included with Apple's clang. It just isn't the abusable one any more; it is a *C* preprocessor, not a Fortran preprocessor. And there is apparently an option to make clang's cpp more permissive, but it is no more recommended than gcc's -traditional for non-C use. (And I don't know if it is permissive enough to handle Fortran.)</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">I should mention that I work with another non-C compiler that similarly abuses cpp --- and similarly broke with clang --- and am still trying to cut through the misunderstandings and politics involved in getting it replaced (we *have* a viable replacement already, just not the will to use it apparently).<br clear="all">
<div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>