Re: How to make c++ realize empty character constant ''?
Oh dear. Just as I went around to do some research, I've realised that what I'm actually talking about is ‘cc’ and not ‘cpp’, just mixed them up. (I couldn't understand, why we couldn't agree.) For quite while I use makefiles instead of the actual command and so this could easily slip my mind. That wasn't what I wanted to say anyways, I just wanted to point out, that g++ (or gcc) is just what it called in the GNU family, and on the Mac, Clang took it's place since Mavericks. With different tools from different vendors, it is called differently. 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? I feel stupid now, and actually I wasn't needed here to begin with, so sorry for the commotion. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
PortAuthority 6.0 released
I've released version 6.0 of PortAuthority, my GUI for MacPorts. This new release includes a number of optimizations for Mavericks (10.9 is now required), Sparkle support, native API's for privilege escalation, better peformance and other improvements. A 30-day demo is available from http://www.codebykevin.com/portauthority.html, and a license costs $30. Free upgrades are always available to registered users. PortAuthority is the only actively-developed, up-to-date GUI for MacPorts, and if you have never tried it out, I encourage you to do so. Thank you, Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to make c++ realize empty character constant ''?
On Sat, Dec 14, 2013 at 6:21 AM, Juhász Ádám jad...@gmail.com wrote: 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? 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.) 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). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
