develooper Front page | perl.perl5.porters | Postings from May 2013

Re: Build failed in Jenkins: perl5 #2285

Thread Previous | Thread Next
From:
Karl Williamson
Date:
May 8, 2013 00:11
Subject:
Re: Build failed in Jenkins: perl5 #2285
Message ID:
51899829.1070302@khwilliamson.com
On 05/07/2013 02:55 AM, Nicholas Clark wrote:
> As to why Jenkins is running g++ not gcc - not sure. There was probably a
> discussion about it at some point, and it was assumed that threaded g++
> would give the most "bang for your buck" in terms of one configuration to
> find the most problems.

Jenkins is running both, and it is running g++ at my request.  And the 
reason was that these types of errors would get into blead and stay 
until someone bothered to compile with g++ (usually me).  We do support 
C++ headers, and the easiest way to do that is to compile the whole 
thing in C++.  Besides, it is possible that the messages from C++ may 
catch problematic constructs that wouldn't work as expected.

I remember when C++ came out; it was billed as a "better C" even if you 
didn't want to use its OO capabilities.  Perhaps C compilers have 
improved in the intervening decades; I don't know.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About