+1 for filesystem (and +10 for using std:: for thread/smart pointers :) *Marco Massenzio* *Distributed Systems Engineer*
On Thu, Apr 23, 2015 at 8:43 AM, Cody Maloney <[email protected]> wrote: > For thread and smart pointer in the coming weeks we'll be able to just use > the standardized versions if we can't already with the move to GCC 4.8 > On Apr 23, 2015 12:59 AM, "Alexander Rojas" <[email protected]> > wrote: > > > I do agree having this discussion. While I wouldn’t be for using every > > single boost library (spirit comes to mind as one we should avoid), using > > libraries like filesystem, thread or smart printers would reduce the > amount > > of code we should maintain, while being certain we are using high quality > > libraries which are widely tested and maintained. > > > > > > > On 22 Apr 2015, at 20:36, Cody Maloney <[email protected]> wrote: > > > > > > It's not header only. > > > > > > I think we actually need a general discussion around upgrading all the > > > libraries mesos depends upon (Using a plain up-stream boost, etc). > > > > > > Note that some portions of stout already require callers to link > against > > > specific libraries for them to actually work, so I don't think the > > > header-only is that big of a requirement. But definitely we should > have a > > > discussion around it. > > > > > > On Wed, Apr 22, 2015 at 9:34 AM, Vinod Kone <[email protected]> > wrote: > > > > > >> Is it header only? > > >> > > >> On Wed, Apr 22, 2015 at 2:31 AM, Alexander Rojas < > > [email protected]> > > >> wrote: > > >> > > >>> Hey guys, > > >>> > > >>> I was checking one of my reviews which call for using some > > unimplemented > > >>> functionality in stout path. Since that class has no methods, > > attributes > > >> or > > >>> anything apart from a string value attribute; I was left wondering, > > >> wether > > >>> it makes sense to use boost filesystem. > > >>> > > >>> Boost filesystem v3 has all the functionality we may need from a path > > >>> class, it is the basis fro a technical recommendation ( > > >>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4100.pdf < > > >>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4100.pdf>) > > and > > >>> might become part of the standard in the future. Why not adopt it in > > >> mesos? > > >>> > > >>> Alexander > > >> > > > > >
