Re: [DynInst_API:] RFC: require users to have C++11

["Mark W. Krentel" <krentel@xxxxxxxx>]

Ok, I was just a bit concerned that when you said C++11 that you meant
to exclude gcc 4.4 and RH 6.x.

In that case, I agree you should bring the include files in line with
how you build Dyninst itself.  Just make a note in the documentation
somewhere.

--Mark



On 08/31/16 15:09, Josh Stone wrote:
> On 08/31/2016 12:07 PM, Mark W. Krentel wrote:
> > Ok, I've been sufficiently taunted.  Speaking as someone who builds a
> > subset of Dyninst (parseapi + symtabapi) from source and applications
> > that use it (Rice HPCToolkit) on a daily basis ....
> Thanks for your input!
>
> > I'm a bit unsure of just what you're suggesting.
> >
> > First, I think it's perfectly ok to require Dyninst clients to build
> > their apps with essentially the same CXXFLAGS (-std=c++11 or
> > -std=c++0x) that you use to build Dyninst.  I'm surprised that you
> > even try to do otherwise.  In HPCToolkit, we already do this and have
> > for a long time.
> Right, so this is the point that I'm suggesting we change.  Despite
> using C++11 internally, Dyninst is currently keeping compatibility with
> non-C++11 users for the public headers. (or at least trying to)
>
> That was probably helpful when Dyninst first transitioned to C++11.
> Now, I think we're far enough along to require it of users too.