April 2013 - Boost - lists.boost.org

[Fusion] another nil issue
by Rich E 23 May '13

23 May '13

I see there was work about 5 months ago to avoid the Obj-C++ nameclash with nil in Boost.Fusion: https://github.com/boostorg/fusion/commit/12d2898287a124ff4b398fd3fff512b6f… Thanks for that as there are alot of use using boost in this scenario. However, I have found another couple nameclashes that prevented me from linking against Boost.Log in the latest trunk on OS X with clang, when trying this sample code: http://boost-sandbox.sourceforge.net/libs/log/example/doc/tutorial_trivial_… Attached is the changeset I needed to make to build. Does this seem acceptable to the maintainers? Best, Rich

2 4

[gil] Ok to merge new gil's extension to release branch?
by Christian Henning 19 May '13

19 May '13

Hi, is it ok? The merge would include io, toolbox, numerics and some other changes to gil's code itself. Regards, Christian

6 92

[GSOC] XML library of Boost
by Amos Ji 12 May '13

12 May '13

Hi All, I'm a graduate student from Fudan University in China. And I hope to contribute some code to Boost during the GSOC. I've scanned the idea page. The ideas in the page are all very interesting and challenging. But what I'm interested in most is XML library, which is at the bottom of page. I think the XML format is the most popular standard for storing information so it's important for Boost to have a good XML library. However, I know Boost contains RapidXML in property_tree library to parse XML file. So what I want to make sure is I need to implement a new XML parser in this project instead of make enhancement for RapidXML. Am I correct? If so, I have some ideas to share with you. In my opinion, an XML parser must be able to do these things: 1. To Iterate over DOM nodes tree; 2. To access the values of nodes and their attributes quickly; 3. To insert or delete nodes or attribute of an exact node easily; 4. To generate new XML from the structure which stores XML in the library. And there are some optional function too: 1. To support XPATH; 2. To validate whether the XML file is valid; 3. To support various encoding; 4. To manage memory better; 5. To support regular expression. The ideas are not mature now. I'll improve them in my proposal. In fact, it's not easy to implement a perfect XML parser but I'll do my best. And I have another question. Who will mentor this XML library project? Thanks for your patience to read this email. Sincerely, Mingchao -- Amos Ji(Mingchao Ji) Master in School of Information Science and Engineering, Fudan University MSN: jmc891205(a)hotmail.com E-mail: jmc891205(a)gmail.com

14 36

[bootstrap/1.53] jam0.exe crashes when bootstrapping for VC2012 AMD64
by rjeczalik 11 May '13

11 May '13

Hi, I'm trying to build Boost 1.53 using VC2012 amd64 (toolset=msvc-11.0 address-model=64) and Windows Server 2012 Standard. Bootstrapping fails with jam0.exe crash - some crash info: Crash stacktrace: ntdll.dll!000007f9bc781069() KernelBase.dll!000007f9b978764e() KernelBase.dll!000007f9b97d3658() jam0.exe!_findnext64i32(__int64 hFile, _finddata64i32_t * pfd) Line 165 jam0.exe!file_dirscan(_object * dir, void (void *, _object *, int, __int64) * func, void * closure) Line 180 jam0.exe!builtin_glob(frame * frame, int flags) Line 718 jam0.exe!function_run(_function * function_, frame * frame, _stack * s) Line 3390 jam0.exe!evaluate_rule(_object * rulename, frame * frame) Line 264 jam0.exe!function_call_rule(_jam_function * function, frame * frame, _stack * s, int n_args, const char * unexpanded, _object * file, int line) Line 468 jam0.exe!function_run(_function * function_, frame * frame, _stack * s) Line 3950 jam0.exe!parse_file(_object * f, frame * frame) Line 57 jam0.exe!main(int argc, char * * argv, char * * arg_environ) Line 488 jam0.exe!__tmainCRTStartup() Line 241 jam0.exe!mainCRTStartup() Line 164 kernel32.dll!000007f9b9de167e() ntdll.dll!000007f9bc7a3501() Line where it crashed was: if (!FindNextFile((HANDLE)hFile, &wfd)) { I've tried to watch the values of arguments passes to FindNextFile() - hFile looked like proper handle, however wfd.cFileName and wfd.cAlternateFileName contained garbage. Is this a known issue for 1.53? I've compiled version 1.52 using the same environment and the same configuration and everything went ok, I did not manage to reproduce the crash. It looks like only version 1.53 is affected. Regards, Rafael Jeczalik

5 5

Re: [boost] [log] Patch: rotating file collector
by Andrey Semashev 10 May '13

10 May '13

On Tue, Apr 23, 2013 at 3:58 PM, Alexander Arhipenko <arhipjan(a)gmail.com>wrote: > > I've added implementation of rotating file collector - > the patch against boost log trunk attached. > This is not the final version, I'm going at least to finish most of the > TODOs. > > However, it would be nice to receive feedback and questions from > library author as well as from people interested in this feature. > > Andrey, could you please find several minutes to review the attached patch? > Thanks for the patch. I didn't look deeply into it yet but from the first glance it looks like you changed the existing file collector rather than introduce an alternative one. Am I right? If so, could this be made as a pure addition rather than modification? I would prefer to keep the current behavior also available for the users. Also, I would like to discuss following question with you : > rotate_file invocation in ~text_file_backend - > I would prefer to have this call during text_file_backend construction > phase. > I'll have to take a closer look later to answer that but it seems odd to have to rotate something when nothing have been written yet. The rotate_file call is intended to place the written file to the storage governed by the collector, and at construction this file hasn't been created yet. Could you describe why you need this?

3 7

[TypeErasure] references
by Chapman, Alec 10 May '13

10 May '13

Hi Steven, I have a somewhat-generic type erasure class that I would like to switch to yours. The main difficulty I can see is in the way capturing by reference is handled. The approach I take in my class is to pass a boost::reference_wrapper to the constructor: typedef mpl::vector<copy_constructible<>, type_id_<>, incrementable<> > requirements; int i = 0; any<requirements> x(boost::ref(i)); // capture i by reference ++x; // i == 1 any<requirements> y(x); // makes a copy of i ++y; // i == 1, any_cast<int>(y) == 2 My motivation is that I have a bunch of template functions already written that I often call directly, but in other cases I need to compile them separately by instantiating them with any<...>: ---------------------- module 1 ------------------------- // some long algorithm that I don't want to modify to be aware of any<...> template<class T> void f(T& t) { ++t; T t2 = t; ++t2; // do something with t2 } // make a type-erased version for separate compilation void any_f(any<requirements>& x) { return f(x); } -------------------- module 2 ---------------------------- // provide a thin wrapper that applies type erasure before calling any_f template<class T> void f_fwd(T& t) { any<requirements> x(boost::ref(t)); any_f(x); } // some function that needs to call f void g(int& i) { // do something with i... // then pass it to f f_fwd(i); } Is something like this possible with your method? Are there advantages that I'm not seeing to having the type signature contain information about whether the object is held by reference? Thanks, Alec

3 6

[log] Is it lock free ?
by adrien courdavault 09 May '13

09 May '13

Hi I'm really interested by the new Log library. I would like to know if there is a part of this API that could be wait free, not the << operator perhaps, but a specific function to log a message without having to worry about a malloc or lock called inside the library. I would like to use this from a time critical thread. thank you

3 5

[predef] Status and review results?
by Rene Rivera 09 May '13

09 May '13

Just a quick message to mention that I've finished all the review related changes to the Predef library. And done some of the future tasks on the library. In particular the addition of endianness definitions and the moving of MinGW as a platform instead of a compiler (and hence the addition of BOOST_PLAT category of macros. And the one question I have is.. When will the review results of the library be decided on? I ask for two reasons. One, the obvious, is just to know if it's accepted or not. And to know if it's not accepted and hence that I should spend time to recreate a "boost/detail/endian.hpp" header that implements the Predef logic for endian detection. Note the project move to Github earlier this year (in preparation for the Boost git move). You can find the project at < https://github.com/grafikrobot/boost-predef>, and browse the current documentation at <http://tinyurl.com/cqqhhev>. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

8 31

[trac] Add component for Boost.Log
by Andrey Semashev 09 May '13

09 May '13

Hi, Not sure whom to ask, but could someone create a component "log" for Boost.Log in Trac? I (andysem) am the maintainer. Thanks.

2 2

[gsoc 2013] draft proposal for chrono::date
by Anurag Kalia 08 May '13

08 May '13

Hi, I mistakenly sent this draft as a reply to personal email of Vicente. I am sorry! Here it is again, verbatim. One related question though. I still haven't got the hang of a Mailing List. Is there a software takes the pain away from it. For example, I use outlook.com and '>' get appended in front of only the start of paragraph making it wholly unreadable. Thanks, Anurag Kalia. ---------------------------------------- > Date: Sat, 27 Apr 2013 18:14:09 +0200 > From: vicente.botet(a)wanadoo.fr > CC: anurag.kalia(a)outlook.com > Subject: Re: [boost] [gsoc 2013] draft proposal for chrono::date > > Le 27/04/13 16:58, Anurag Kalia a écrit : > >> I understand that you want to design your own library, I did the same, > >> but getting a coherent design would take you some time. > >> I suggest you to start with the H. Hinnant proposal as a reference and > >> state what you want to added, changed or removes. State clearly why do > >> you want these changes, what would be improved/solved. > >> > >> Don't forget to inspect the threads/discussion related to the H.Hinnant > >> proposal, and the paper N3344 Toward a Standard C++ 'Date' Class > >> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3344.pdf > > Hi Vicente, > > > > Thanks a lot for the exhaustive reply! I will get back to you after going through all the things you pointed out and also the paper you forwarded. But I have one quick question for now, from where can I start my search for the threads and discussions around this date proposal? > > > > > > > Hi, > > There were some interesting exchanges in > https://groups.google.com/forum/?fromgroups=#!forum/kona-date-lib > > I guess that if you request to the administrator s/he will be able to > give you read access to the existing threads (there are not too much). > > Best, > Vicente > I have finally implemented some representative functions in date class and calendar to get a better idea of the proposal. I have dropped the JDN storage for another implementation that I thought of in the middle of the night. I think it is a hybrid approach between serial and field-based implementations. Off the top of my head, without any alternative implementations at hand and benchmarks too, I can't think of something inherently wrong in it. I would really like to hear its gotchas, if any. I have overhauled my proposal on the basis of it. It doesn't contain other headings like about me etc for today. I have tried to incorporate all the previous points you noted before and have also tried to keep naming consistent. I did use uppercase constants in there but they are meant to be private. Is that okay? I knew little about the benchmarks before you sent me that paper. From what I got, they just iterate over a significant period of time and note the start and ending time. Is it more than that? And should I make them before or after I have multiple implementations in hand. I could get hold of your and Howard Hinnant's implementations for them, but then the APIs would have to line up, wouldn't they? Hope you find my proposal better this time around. With an open ear, Anurag Kalia.

9 95