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

Re: Build failed in Jenkins: perl5 #2285

Thread Previous | Thread Next
From:
Craig A. Berry
Date:
May 8, 2013 17:20
Subject:
Re: Build failed in Jenkins: perl5 #2285
Message ID:
CA+vYcVxUm2C73yERQUMC2r361pcSZV7Qoxdtz9EKb+xKwXR9hw@mail.gmail.com
On Wed, May 8, 2013 at 2:04 AM, Nicholas Clark <nick@ccl4.org> wrote:

>
> On Tue, May 07, 2013 at 06:11:21PM -0600, Karl Williamson wrote:
>
> > 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.
>
> Yes, we need to test that the headers are clean for C++.
> We didn't use to, and we certainly screwed it up once (The 5.8.8 release,
> IIRC)
>

C++ also forces explicitness about which symbols are external and which
aren't, and that can help ensure that everything gets exported that's meant
to and nothing gets exported that isn't meant to (and the latter can limit
the proliferation of accidental APIs).

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