June 2004 - Boost-users - lists.preview.boost.org

ternary search trie
by Sybrand Badenhorst 28 Jun '04

28 Jun '04

Hi, Does the BOOST library (somewhere) contain a ternary search trie container type (as described by Robert Sedgewick in his "Algorithms - 3ed edition" or here: http://www.cs.princeton.edu/~rs/strings/) that can by used as a standalone container (such as for example STL's map) ? I don't find something like this listed on the Boost library page (http://www.boost.org/libs/libraries.htm). Any help will be greatly appreciated, Thanks Sybrand

3 3

Spirit problem
by Michael Orlov 28 Jun '04

28 Jun '04

Hi, I am new to Spirit, and I am writing a reader for s-expressions, and so far has encountered the following problems, which seem to me to be contrarry to the documentation (Spirit 1.8.0 in Boost 1.31.0). Consider the following (small) C++ program: --------------------------------------------- #include <iostream> #include <iterator> #include <string> #include <boost/spirit/core.hpp> #include <boost/spirit/iterator/multi_pass.hpp> using namespace std; using namespace boost::spirit; struct Sexp : public boost::spirit::grammar<Sexp> { template <typename ScannerT> struct definition { typedef rule<ScannerT> rule; definition(const Sexp &self) { first = ( sexp = '(' >> *sexp >> ')' ); } subrule<0> sexp; rule first; const rule& start() const { return first; } }; }; int main() { typedef std::istream_iterator<char> iterator_t; typedef boost::spirit::multi_pass< iterator_t, boost::spirit::multi_pass_policies::input_iterator, boost::spirit::multi_pass_policies::first_owner > iterator_wrapper_t; Sexp sexper; iterator_t under_first(cin); iterator_t under_last; iterator_wrapper_t first(under_first); iterator_wrapper_t last(under_last); while (true) { parse_info<iterator_wrapper_t> info = parse(first, last, sexper); first.clear_queue(); if (info.hit) std::cout << "Hit: " << info.length << std::endl; else break; }; } --------------------------------------------- The purpose is to read s-expression from input, delivering them to the user the moment they are ready. Since whitespace skipper tries to consume as much space as it can, it is not suitable here, so I don't want to use it. Here comes the first problem: even when I don't pass space_p to parse(), the skipper is still present: --- ( ) ^D Hit: 2 --- --- (())( Hit: 4 ) ^D Hit: 2 --- Another problem is when I try to use istreambuf_iterator instead of istream_iterator (this is done in Spirit examples, too). When substituting istreambuf_iterator in the first typedef in main(), the program no longer compiles - neither with Intel Compiler 8.0.055, nor with GCC 3.3.2. Intel complains about /usr/local/include/boost/spirit/iterator/multi_pass.hpp(537): error: initial value of reference to non-const must be an lvalue return **input; and GCC's messages are too long to parse. :) Any help? Thanks, Michael

2 1

Using Regex
by kinshuk srivastava 27 Jun '04

27 Jun '04

Hi I have installed the boost 1.31.0 and have been trying to compile the test examples that were there in the regular expression library.But the compiler isnt able to identify the header files.So I did include the path during my compilation by using the -I and the path name..However it is still inable to compile as it is unable to include or search the indented header files... This is my first time I have been using this kind of library.Can someone suggest a way so that I can start using the library.Is there a way in which I can directly compile nad run the files without having to go through the ordeal of specifying the path at compile time everytime I wanna use the file Any help will be highly appreciated. Sincerely -Kinshuk ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/

2 1

Automake/Autoconf rules for boost libs
by Sebastian Stein 27 Jun '04

27 Jun '04

Hi folks, is somewhere documented how to add automake/autoconf stuff for boost to a project? I have a set of small testcases and the need boost_unit_test_framework-gcc library to compile. At the moment I add the lib directly to linker options with project_test_LDADD = -lboost_unit_test_framework-gcc But this is not platform independent, because someone might have not gcc installed. So how can I do it in a better way? Sebastian

5 5

[Fwd: [subgraph] unable to set graph properties using set_property() method]
by LOU Wenwu 27 Jun '04

27 Jun '04

Hi, I was trying to set graph properties, such as a meaningful name, to individual subgraphs, but the following test code failed. ====================================== typedef adjacency_list<v ecS, vecS, directedS, no_property, no_property no_property, property<graph_name_t, std::string> > graph_t; typedef subgraph<graph_t> subgraph_t; graph_t g; boost::set_property(g, graph_name, "a graph"); // **this worked, of course subgraph_t sg; boost::set_property(g, graph_name, "subgraphs"); // ** Error C2784 Error C2784: could not deduce template argument... ======================================= I used the BGL came with Boost 1.30.0 in .NET 2003. Any idea of how to make it work? Thanks, Daniel

1 0

Newbie question: add_edge()
by Tim Rowe 27 Jun '04

27 Jun '04

Thanks for all the help so far. I'm not there yet, though! The documentation for add_edge() says that the first two parameters are of type boost::graph_traits<G>::vertex_descriptor. In the example in quick_tour.html it is called with integers (from an enum) as its first two parameters. Is that because: i. add_edge is overloaded to take integers as the first two parameters; ii. boost::graph_traits<G>::vertex_descriptor just happens to be an integer type in this case; iii. boost::graph_traits<G>::vertex_descriptor is /always/ an integer type; or iv. some other reason I haven't thought of. Thanks in advance.

2 3

Problem
by przemyslaw.sliwa＠gazeta.pl 26 Jun '04

26 Jun '04

Dear All, I am a beginner with Boost and hae compiled the library on my suse 9.0 Athlon-m machine. I can compile the programs and link them (using Kdevelop) but if I invoke the programm I am getting a strange error which shows me that the shared library libboost_date_time-gcc-1_31.so.1. 31.0 cannot be loaded. This is somehow strange since I have linked against the static library using the argument -lboost_date_time-gcc. The boost install process compile a big rane of libraries and I am ot familar ith them. Can you help me with this issue??? Thank you very much for any kind of help, Przemyslaw

1 0

problem compiling with Dinkumware
by Jean-Pierre Gygax 26 Jun '04

26 Jun '04

Hi, I'm having trouble properly compiling Boost with the Dinkumware STL implementation (working with Visual C++ 7.1). The problem is that bjam always calls CL with a /I that pulls in Microsoft's include files first, so that they take precedence over the Dinkumware ones. This behavior seems to be rooted far down in the file Jambase located in jam_src. I don't really feel like fooling with that. What can I do? -- Jean-Pierre

3 5

Tweaking the Skip Parser, was RE: [Boost-users] Spirit 1.6 with VC6
by Mark Storer 26 Jun '04

26 Jun '04

> No chance of switching to 7.1? :-) Things are looking up. We just did a project-wide upgrade to... VC7.1. Problem solved. I'm now merrily writing rules for my JavaScript parser. It doesn't have to support the whole language (not for a while, maybe never), I just need to be able to parse out the names and locations of all the functions in a file. It's for a JavaScript editor built into one of our products, and later we'll be adding auto-completion. That'll require a more thorough parser, but for now, I'm just after funciton locations. So far so good... though I'll undoubtedly be quite familiar with the BOOST_SPIRIT_DEBUG* macros before I'm done. I've got another Spirit question: I've been adding "*comment" throughout the rules and it's getting tiresome: rule<phrase_scanner_t> blockComment = comment_p( "/*", "*/" ); rule<phrase_scanner_t> lineComment = comment_p( "//" ); rule<phrase_scanner_t> comment = blockComment | lineComment; Spraying the "comment" rule liberally through my rules is an option... rule<phrase_scanner_t> codeBlock = ch_p('{') >> *(comment | codeBlock | ~ch_p('}')) >> ch_p('}'); ... but not an appealing one. This becomes particularly true once I start working on the auto-completion parser. It just occured to me that if the skip parser ate comments for me, it would greatly simplify my rules. I'd like to tweak the skip parser so it skips over my "comment" rule as well as white space. I just took a stab at this, but didn't get very far. I tried: parse(str, rules, space_p | comment) but that resulted in a compiler error. 7.1's errors are MUCH easier to read that 6's. I'm going to like this new compiler. C:\SDKs\boost_1_31_0\boost\spirit\core\non_terminal\impl\rule.ipp(190): error C2664: 'boost::spirit::impl::abstract_parser<ScannerT,AttrT>::do_parse_virtual' : cannot convert parameter 1 from 'const scanner_t' to 'const boost::spirit::rule<T0>::scanner_t &' with [ ScannerT=boost::spirit::rule<boost::spirit::phrase_scanner_t>::scanner_t, AttrT=boost::spirit::rule<boost::spirit::phrase_scanner_t>::attr_t ] and [ T0=boost::spirit::phrase_scanner_t ] Pointing me to the relevant section of the docs is an acceptable answer, though I wouldn't mind a little more info than that. ;) I'll keep plugging away. If I come up with an answer, I'll post it to the list. I'd expect this to be useful to other beginners at the very least. --Mark Storer Senior Software Engineer Verity, Inc.

3 3

RE: [Boost-users] Re: Tweaking the Skip Parser, was RE: Spirit 1.6 with VC6
by Mark Storer 25 Jun '04

25 Jun '04

Okay. Problem solved. The answer was indeed inside #scanner_business. Rules make for picky parsers. So I used a grammar<> and it compiled just fine. Now if I can just get it to WORK. ;) Whoops. Infinite recursion. Back to the drawing board... but at least now I don't need "*comment" sprinkled liberally throughout my rules. --Mark Storer Senior Software Engineer Verity, Inc. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org]On Behalf Of Jeff Flinn > Sent: Friday, June 25, 2004 10:46 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Re: Tweaking the Skip Parser,was RE: Spirit 1.6 > with VC6 > > > Take a look at: > > http://www.boost.org/libs/spirit/doc/faq.html#scanner_business > > You don't want the skip parser to be a phrase level scanner. > > parse(str, rules, space_p | comment_p( "/*", "*/" ) | > comment_p( "//" ) ) > > may work for you? > > Jeff F > > "Mark Storer" <MStorer(a)verity.com> wrote in message > news:076D1E704127414E9FEAFFC31F66C9472739CD@vrsdex1.verity.com... > > > No chance of switching to 7.1? :-) > > > > Things are looking up. We just did a project-wide upgrade > to... VC7.1. > Problem solved. I'm now merrily writing rules for my > JavaScript parser. It > doesn't have to support the whole language (not for a while, > maybe never), I > just need to be able to parse out the names and locations of all the > functions in a file. It's for a JavaScript editor built into > one of our > products, and later we'll be adding auto-completion. That'll > require a more > thorough parser, but for now, I'm just after funciton locations. > > > > So far so good... though I'll undoubtedly be quite familiar with the > BOOST_SPIRIT_DEBUG* macros before I'm done. > > > > I've got another Spirit question: I've been adding > "*comment" throughout > the rules and it's getting tiresome: > > > > rule<phrase_scanner_t> blockComment = comment_p( "/*", "*/" ); > > rule<phrase_scanner_t> lineComment = comment_p( "//" ); > > rule<phrase_scanner_t> comment = blockComment | lineComment; > > > > Spraying the "comment" rule liberally through my rules is > an option... > > > > rule<phrase_scanner_t> codeBlock = ch_p('{') >> > *(comment | codeBlock > | ~ch_p('}')) >> ch_p('}'); > > > > ... but not an appealing one. This becomes particularly > true once I start > working on the auto-completion parser. > > > > It just occured to me that if the skip parser ate > comments for me, it > would greatly simplify my rules. I'd like to tweak the skip > parser so it > skips over my "comment" rule as well as white space. I just > took a stab at > this, but didn't get very far. I tried: > > > > parse(str, rules, space_p | comment) > > > > but that resulted in a compiler error. 7.1's errors are > MUCH easier to > read that 6's. I'm going to like this new compiler. > > > > > C:\SDKs\boost_1_31_0\boost\spirit\core\non_terminal\impl\rule. > ipp(190): > error C2664: > 'boost::spirit::impl::abstract_parser<ScannerT,AttrT>::do_pars > e_virtual' : > cannot convert parameter 1 from 'const scanner_t' to 'const > boost::spirit::rule<T0>::scanner_t &' > > with > > [ > > > ScannerT=boost::spirit::rule<boost::spirit::phrase_scanner_t>: > :scanner_t, > > > AttrT=boost::spirit::rule<boost::spirit::phrase_scanner_t>::attr_t > > ] > > and > > [ > > T0=boost::spirit::phrase_scanner_t > > ] > > > > Pointing me to the relevant section of the docs is an > acceptable answer, > though I wouldn't mind a little more info than that. ;) > > > > I'll keep plugging away. If I come up with an answer, I'll > post it to the > list. I'd expect this to be useful to other beginners at the > very least. > > > > --Mark Storer > > Senior Software Engineer > > Verity, Inc. > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0