- Boost - lists.boost.org

[tokenizer] offset_separator does not behave as docs state it does
by Bart 02 Aug '05

02 Aug '05

The docs for the offset_separator state the following regarding the breturnpartiallast construction parameter: "For example the string "122501" with offsets (2,2,4) ... With it set to false, it will parse to 12 25 and then will stop because there are only 2 characters left in the sequence instead of the 4 that should have been there." This leads me to believe, the string "1225011" (3 chars in last part) should also stop parsing after the first two tokens and ignore the third. It does not. Using the following example (compiled against current cvs)... int main(){ using namespace std; using namespace boost; string s = "1225199"; int offsets[] = {2,2,4}; offset_separator f(offsets, offsets+3, false, false); tokenizer<offset_separator> tok(s,f); for(tokenizer<offset_separator>::iterator beg=tok.begin(); beg!=tok.end();++beg){ cout << *beg << "\n"; } } Output is: 12 25 199 I think it should be just: 12 25 Thanks, Bart

1 0

1.33.0 Release, why not Beta it first?
by Michael Goldshteyn 02 Aug '05

02 Aug '05

I am going to once again raise the issue of putting the releases into Beta, prior to making a final (6-9 month) release. Perhaps we need a policy of the release being in a final Beta built form for some period, say 2-4 weeks, prior to the final release. I think this will allow people who wait for a packaged version to experiment with any newly added features, fixes, etc... and report issues that can be resolved in the final release, but were not made visible by the regression tests. Just my opinion, Mike

3 2

[1.33.0] User reports go live / feedback request
by Aleksey Gurtovoy 02 Aug '05

02 Aug '05

The following message is a courtesy copy of an article that has been posted to gmane.comp.lib.boost.testing as well. The draft version of user-centric regression reports is now available at http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/user/summar… (http://tinyurl.com/bamym) If you'd like to comment on usability/presentation of these before they go public with the release, now it's time :). -- Aleksey Gurtovoy MetaCommunications Engineering

3 5

[Boost-bugs] [ boost-Bugs-1250022 ] Spelling error in error message
by SourceForge.net 02 Aug '05

02 Aug '05

Bugs item #1250022, was opened at 2005-08-02 00:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250022&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: Spelling error in error message Initial Comment: In basic_archive.hpp, line 21: #error "no serialization headers my precede any archive headers" should be "may", not "my" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250022&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X< Y >
by Brian Braatz 02 Aug '05

02 Aug '05

Suggestion: is there some way in your design you can get away with deriving from the incomplete type to "de-incomplete" it? > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Andreas Huber > Sent: Monday, August 01, 2005 3:33 AM > To: boost(a)lists.boost.org > Subject: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X< Y > > > > Hi there > > I'm trying to address a point raised by Jonathan Turkanis during the > formal review of the statechart library. Basically, the problem boils > down to the following: > > #include <boost/mpl/list.hpp> > #include <boost/mpl/size.hpp> > #include <boost/mpl/as_sequence.hpp> > > namespace mpl = boost::mpl; > > // InnerInitial is either an mpl sequence of types or a single type > template< class InnerInitial > > struct state > { > // stateArray_ must have a length equal to the number of types > // in InnerInitial > int stateArray_[ > mpl::size< > typename mpl::as_sequence< InnerInitial >::type > >::type::value > ]; > }; > > // A is defined later, possibly in a different translation unit > struct A; > > template< class X > > struct B > { > typedef typename X::reactions reactions; > }; > > int main() > { > // fine: instantiation with an incomplete type > state< A > a; > // fine: instantiation with an mpl sequence containing B< A > > state< mpl::list< B< A > > > b; > // error: mpl::as_sequence triggers the instantiation of B's member > // typedef, which tries to access the member typedef of A. A compile- > // time error results because A is still incomplete at this point. > state< B< A > > c; // *** here *** > > return 0; > } > > MSVC7.1 and GCC3.4 agree that the last state template instantiation is > illegal (use of undefined type A). I'm wondering whether there is any > way to make this legal (different as_sequence implementation, implement > the state template differently, etc.)? > > Thanks & Regards, > > -- > Andreas Huber > > When replying by private email, please remove the words spam and trap > from the address shown in the header. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] [ANN] xpressive 0.9.5 in boost-sandbox
by Brian Braatz 02 Aug '05

02 Aug '05

Nice work! (I especially like the static expressions :) ) Any feel for when you will be ready for formal review? > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Eric Niebler > Sent: Monday, August 01, 2005 8:24 PM > To: Boost mailing list > Subject: [boost] [ANN] xpressive 0.9.5 in boost-sandbox > > << Background >> > xpressive is a TR1 regex work-alike that also accepts regexes as > expression templates and lets regexes nest and call each other > recursively. > > << Significant changes since 0.9.3 >> > - c_regex_traits to wrap the global C locale > - null_regex_traits for searching non-char data > - doc and test improvements > - bugs in static regexes and Unicode support squashed > > << Download >> > xpressive.zip at: > http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler > > << Docs >> > http://boost-sandbox.sf.net/libs/xpressive > > Note: You can consider this the xpressive 1.0 release candidate. All > that remains is to add more tests and documentation, and perhaps a tweak > to the traits interface. > > -- > Eric Niebler > Boost Consulting > www.boost-consulting.com > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[ANN] xpressive 0.9.5 in boost-sandbox
by Eric Niebler 02 Aug '05

02 Aug '05

<< Background >> xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. << Significant changes since 0.9.3 >> - c_regex_traits to wrap the global C locale - null_regex_traits for searching non-char data - doc and test improvements - bugs in static regexes and Unicode support squashed << Download >> xpressive.zip at: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler << Docs >> http://boost-sandbox.sf.net/libs/xpressive Note: You can consider this the xpressive 1.0 release candidate. All that remains is to add more tests and documentation, and perhaps a tweak to the traits interface. -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0

Re: [boost] Interest in an ODBC library?
by Brian Braatz 02 Aug '05

02 Aug '05

Joaquin, sorry for the few days response here- I had a "surprise" business trip I had to take which kept me out of town and away from mail for a few days Thoughts below (note- I have left a good chunk of the original mail intact for context) > -----Original Message----- > On Behalf Of Joaquin M Lopez Munoz > > Brian Braatz <brianb <at> rmtg.com> writes: > > If you would please elaborate. (some of us are "slower" than others :) > > ). > > > > is the problem getting to the index objects themselves via > > inherit_linearly? > > > > if you have dynamic data, then I am thinking you also have dynamically > > applied indices? > > > > Maybe I can elaborate- > > > > consider the following pseudo code: > > > > connection con = db.connect("myserver,root,password,mydatabase"); > > > > dynamic_table dt; > > > > // the select "*" means bring me back all the fields from that table > > // even though I don't know what the fields ARE yet > > dt = query("select * from person"); > > > > // ok so now dt has an UNKNOWN number of columns > > > > dt.add_index( index("first_name")); > > > > // or something along those lines. > > > > in this case, the index is applied dynamically. > > > > so how does that connect with the things you said ? > > > [Joaquin M Lopez Munoz Writes:] > Let me formulate the problem in the terminology > of Boost.MultiIndex --hopefully, the implications > for a DB framework scenario will be clear after this. > > Consider the following perfectly normal code dealing > with a static multi_index_container: > > typedef multi_index_container< > element, > indexed_by< > ordered_unique<identity<element> >, > sequenced<> > > > > static_mic_t; > > template<typename Index> > void reverse_dump(const Index& i) > { > std::copy( > i.rbegin(),i.rend(), > std::ostream_iterator<typename Index::value_type>(std::cout)); > } > > int main() > { > static_mic_t s_mic; > ... > reverse_dump(s_mic.get<0>()); > reverse_dump(s_mic.get<1>()); > } > > What would the equivalent be for the dynamic case? > > typedef dynamic_multi_index_container< > element > > dynamic_mic_t; // no indices specified at compile time > > int main() > { > dynamic_mic_t d_mic; > > // add indices at run time > d_mic.add_index<ordered_unique<identity<element> > >(); > d_mic.add_index<sequenced<> >(); > ... > > reverse_dump(d_mic.get(0)); // note index number is no longer > reverse_dump(d_mic.get(1)); // a template parameter > } > > Now, how are we supposed to define reverse_dump? Clearly > it cannot be the same template as in the static case, > since the types of the indices are only known at > run time. [Brian Braatz Writes:] ideas- have the container accept a list of possible index types then use inherit_linearly<> to make those types- (only as pointers) then when the index gets runtime added- you store it in the generated objects Additionally- one could also force the user to make a struct to use as a tag to reference the index (instead of the number) using this "type tag", you can lookup the runtime object(s) which were dynamically added. What I am suggesting is a similar design to what I recently got working on something else (almost ready for sharing with the world). I have yet another plan trip tomorrow (ALL DAY tomorrow). I will code a small sample of what I am suggesting. (code is easier to talk about than concepts sometimes :) ) Joaquín M López Muñoz writes: > If I wasn't clear enough please tell me so and > I'll try to elaborate. I'll be more than happy to > discuss and refine these ideas. IMHO the concepts > around a potential multi_index_container sketched > here can serve as the basis for a DB run-time data > structure, much like for instance IndexedDBView in the > DTL does. > > Best, > > Joaquín M López Muñoz > Telefónica, Investigación y Desarrollo I am not as familiar with multi-index, but I am going to re-re-rereview that lib tomorrow along with the mail you wrote. Pleasure "talking" with you :) Brian

1 0

Still Can't Build Docs
by David A. Greene 02 Aug '05

02 Aug '05

I'd like to put the NTP library up on the sandbox but I need to be able to build documentation first. I updated to the latest CVS, build bjam and here's what I get: >>-waller-> which bjam /home/greened/bin/bjam >>-waller-> pwd /home/greened/src/boost/doc >>-waller-> bjam --v2 warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). /home/greened/src/boost/tools/build/v2/tools/boostbook.jam:319: in object(boostbook-generator)(a)1.run warning: rulename $(base-target).depends expands to empty string /home/greened/src/boost/tools/build/v2/build/generators.jam:826: in try-one-generator-really /home/greened/src/boost/tools/build/v2/build/generators.jam:873: in try-one-generator /home/greened/src/boost/tools/build/v2/build/generators.jam:1080: in construct-really /home/greened/src/boost/tools/build/v2/build/generators.jam:1139: in generators.construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1242: in construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1128: in object(typed-target)(a)22.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:757: in generate-really /home/greened/src/boost/tools/build/v2/build/targets.jam:730: in object(main-target)(a)1.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:252: in object(project-target)(a)17.generate /home/greened/src/boost/tools/build/v2/build-system.jam:276: in load /home/greened/src/boost/tools/build/v2/kernel/modules.jam:259: in import /home/greened/src/boost/tools/build/v2/kernel/bootstrap.jam:153: in boost-build /home/greened/src/boost/boost-build.jam:12: in module scope /home/greened/src/boost/tools/build/v2/tools/boostbook.jam:324: in object(boostbook-generator)(a)1.run warning: rulename $(target[2]).set-path expands to empty string /home/greened/src/boost/tools/build/v2/build/generators.jam:826: in try-one-generator-really /home/greened/src/boost/tools/build/v2/build/generators.jam:873: in try-one-generator /home/greened/src/boost/tools/build/v2/build/generators.jam:1080: in construct-really /home/greened/src/boost/tools/build/v2/build/generators.jam:1139: in generators.construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1242: in construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1128: in object(typed-target)(a)22.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:757: in generate-really /home/greened/src/boost/tools/build/v2/build/targets.jam:730: in object(main-target)(a)1.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:252: in object(project-target)(a)17.generate /home/greened/src/boost/tools/build/v2/build-system.jam:276: in load /home/greened/src/boost/tools/build/v2/kernel/modules.jam:259: in import /home/greened/src/boost/tools/build/v2/kernel/bootstrap.jam:153: in boost-build /home/greened/src/boost/boost-build.jam:12: in module scope /home/greened/src/boost/tools/build/v2/tools/boostbook.jam:325: in object(boostbook-generator)(a)1.run warning: rulename $(target[2]).depends expands to empty string /home/greened/src/boost/tools/build/v2/build/generators.jam:826: in try-one-generator-really /home/greened/src/boost/tools/build/v2/build/generators.jam:873: in try-one-generator /home/greened/src/boost/tools/build/v2/build/generators.jam:1080: in construct-really /home/greened/src/boost/tools/build/v2/build/generators.jam:1139: in generators.construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1242: in construct /home/greened/src/boost/tools/build/v2/build/targets.jam:1128: in object(typed-target)(a)22.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:757: in generate-really /home/greened/src/boost/tools/build/v2/build/targets.jam:730: in object(main-target)(a)1.generate /home/greened/src/boost/tools/build/v2/build/targets.jam:252: in object(project-target)(a)17.generate /home/greened/src/boost/tools/build/v2/build-system.jam:276: in load /home/greened/src/boost/tools/build/v2/kernel/modules.jam:259: in import /home/greened/src/boost/tools/build/v2/kernel/bootstrap.jam:153: in boost-build /home/greened/src/boost/boost-build.jam:12: in module scope /home/greened/src/boost/tools/build/v2/build/targets.jam:1245: in construct from module object(typed-target)@22 error: unable to construct ./doc /home/greened/src/boost/tools/build/v2/build/targets.jam:1128: in object(typed-target)(a)22.generatefrom module object(typed-target)@22 /home/greened/src/boost/tools/build/v2/build/targets.jam:757: in generate-really from module object(main-target)@1 /home/greened/src/boost/tools/build/v2/build/targets.jam:730: in object(main-target)(a)1.generate from module object(main-target)@1 /home/greened/src/boost/tools/build/v2/build/targets.jam:252: in object(project-target)(a)17.generate from module object(project-target)@17 /home/greened/src/boost/tools/build/v2/build-system.jam:276: in load from module build-system /home/greened/src/boost/tools/build/v2/kernel/modules.jam:259: in import from module modules /home/greened/src/boost/tools/build/v2/kernel/bootstrap.jam:153: in boost-build from module /home/greened/src/boost/boost-build.jam:12: in module scope from module I edited tools/build/v2/user-config.jam to use the gcc toolset. Any ideas? -Dave

1 0

[1.33.0] Partial thaw on branch for fixing the remaining failures
by Doug Gregor 02 Aug '05

02 Aug '05

The RC_1_33_0 branch is partially thawed so that we can fix the remaining failures for release. I've started the regression notifications again, this time on the release branch: when no more failures show up, we release. Library authors: for any failures that you will not fix, mark them as expected failures on the branch. If you believe there is a configuration problem on one of the test machines, write to the list to say what you think is going on and we'll try to get it fixed. The list of issues we need to fix before we can release is here: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/ developer/issues.html Doug

8 15