gmane.comp.parsers.spirit.devel

Re: [spirit2] namespaces

Andy Elvey — 2008-12-03T08:37:29

( snip ) I also agree. This looks like a really clean way of doing things. - Andy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit2] namespaces

OvermindDL1 — 2008-12-03T04:29:15

Yea, VS by default is slow, but that is mostly due to how it handles completion and such. Visual Assist kills that and uses its own, absolute worlds better, a bit of cacheing time upon install and global header changes, all perfect. :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit2] namespaces

Carl Barron — 2008-12-03T02:14:14

On Dec 2, 2008, at 8:23 PM, Joel de Guzman wrote: I don't use any of the above and my 'free' tools don't auto choose a namespace. [At least I don't think they do:)] I don't use windows* for that matter. I could but I don't. <\NOt_BASHING> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit2] namespaces

Joel de Guzman — 2008-12-03T01:23:39

I use Visual Studio's compiler, but not the text editor. For me, it's too slow. It's response is sluggish (to say the least). Me, I prefer a bare-bones text editor like SciTE. You know... preferences... ;-) Eclipse? I find it rather sluggish too. Perhaps due to Java? Yet it seems to be in the same league as VS in terms of slugishness. Hey, I'm not bashing here. It's just my observation. I do find the MS compiler to be one of the best, if not the best. Herb did good! Regards,

Re: [spirit2] namespaces

OvermindDL1 — 2008-12-02T20:29:57

On Tue, Dec 2, 2008 at 7:05 AM, Joel de Guzman boost-consulting.com> wrote: If you all see a need for it then go for it. :P Eclipse (or insert whatever is your preferred dev environment) really needs something like Visual Assist; for C++ programming the difference is night and day... ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit2] namespaces

Joel de Guzman — 2008-12-02T14:05:57

Is it at least fair to say that for us poor souls without such a utility, such an approach I outlined is good :-) Regards,

Re: [spirit2] namespaces

OvermindDL1 — 2008-12-02T07:01:50

It actually matters not to me. I program in Visual Studio 2k5 with the Visual Assist addon (absolutely addicted to it), regardless of what platform I compile on, and it lets me know where things are located so I never need to go looking (I am still looking for something for Eclipse that does even half of what Visual Assist does... nothing was even close last I checked a year ago...). If you have a good enough IDE (like with Visual Assist), then it makes up for API oddities quite well without ever noticing. :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit 2] create and fusionize struct

Joel de Guzman — 2008-12-02T05:36:19

Thank You! :-)

Re: [spirit 2] create and fusionize struct

Carl Barron — 2008-12-02T04:40:32

On Dec 1, 2008, at 9:17 PM, Joel de Guzman wrote: attached is a mdified section describing BOOST_FUSION_STRUCT I used a text editor but the tags seem self explanatory so its is in quick book format but is only a section. [section:create_and_adapt_struct BOOST_FUSION_STRUCT] [heading Description] BOOST_FUSION_STRUCT is a macro that can be used to generate all the necessary boilerplate to make an arbitrary struct and covert it into a __random_access_sequence__. [heading Synopsis] BOOST_FUSION_STRUCT( struct_name (member_type0, member_name0) (member_type1, member_name1) ... ) [heading Semantics] The above macro generates the struct struct_name and necessary code to adapt `struct_name` as a model of __random_access_sequence__. The sequence of `(member_typeN, member_nameN)` pairs declare the type and names of each of the struct members that will be part of the sequence. The macro should be used at global scope, and `struct_name` should be the fully names

Re: [spirit2] namespaces

Carl Barron — 2008-12-02T03:00:38

On Dec 1, 2008, at 9:10 PM, Joel de Guzman wrote: great idea ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Re: [spirit2] namespaces

Matthias Vallentin — 2008-12-02T02:49:00

I found myself many times in this situation. This looks clean and helpful, from a usability perspective. My vote goes for it. Matthias

Re: [spirit 2] create and fusionize struct

Joel de Guzman — 2008-12-02T02:17:17

Cool! I think that's sufficient. But, hey, don't forget the docs, ok. You can simply rip the adapt_struct docs, if you want. Regards,

Re: [spirit 2] create and fusionize struct

Joel de Guzman — 2008-12-02T02:13:07

Hey, you should keep your copyright ;-) Regards,

[spirit2] namespaces

Joel de Guzman — 2008-12-02T02:10:59

Hi, namespaces... I find it a bit cumbersome to use lots of components in spirit2 placed in different namespaces. For example, in what namespace is "rule" in? How about "unused"? "lit"? etc. Many times, it's not clear where one component lives. I do like the way we have ascii, iso8859_1 and soon unicode. But others are rather, ehm, placed adhoc-y. For example, while arg_names::_1 is ok, arg_names::_val and arg_names::_a are not! Those are not arguments! I want to clean these up, so be prepared for namespace name changes. Also, I'm not quite happy with the situation where the user needs to refer to the docs to know which namespace a particular component lives in. So... I am really contemplating on hoisting all public components used by a particular module, except the character-set related components, in the namaspaces qi, karma, or lex. For example: namespace boost { namespace spirit { namespace qi { using boost::spirit::int_; }}} That way, when using Qi, for example, you can use the boost::spirit:

Re: [spirit 2] create and fusionize struct

Carl Barron — 2008-12-02T01:53:29

On Dec 1, 2008, at 7:02 PM, Joel de Guzman wrote: Ok tthe extra includes go away ok DEFINE_STRUCT -> BOOST_FUSION_STRUCT and your copywrite /license added. Probably since it was once cut from a testing main file:) its not needed Docs same as BOOST_FUSION_ADAPT_STRUCT except it also creates the struct. attached is modifed crteate_strict.h. maiin.cpp - simple tests results.txt my results of my runs. tested with fusion:::for_each,fusion::at_c any others fusion operations needed to test?? Last login: Mon Dec 1 19:22:57 on console localhost:~ carlbarron$ cd xcode_worrk/test_create -bash: cd: xcode_worrk/test_create: No such file or directory localhost:~ carlbarron$ cd xcode_work/test_create localhost:test_create carlbarron$ cd build/release localhost:release carlbarron$ ls test_createtest_create.dSYM localhost:release carlbarron$ ./test_create test of ex1 2 example 1 end of test of ex1 test of ex2 2 example 1 4 example 2 end of test of ex2 localhost:release carlbarron$ .

Re: [spirit 2] create and fusionize struct

Joel de Guzman — 2008-12-02T00:02:27

Cool! Some comments: * Don't include . That is expensive. Include only what's needed. Actually, simply including adapt_struct.hpp is enough to give you what you need from PP. * If you intend that to be part of fusion, then the name should be BOOST_FUSION_STRUCT * Why do you need to include ? If you want them added to fusion, I'll need: 1) Some tests 2) Docs I'll add a page for acknowledging contributions. Thanks! Regards,

[spirit 2] create and fusionize struct

Carl Barron — 2008-12-01T19:22:57

Atteached is a macro I use to create 'simple' structs and make fusion sequences of them ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ Spirit-devel mailing list Spirit-devel< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spirit-devel

howto feed inputs to examples? (was Re: Spirit2x inSpirit SVN

Larry Evans — 2008-12-01T17:53:19

In: https://spirit.svn.sourceforge.net/svnroot/spirit/trunk/Spirit2x/libs/spirit/example/qi/ there's subdirectories with, apparently, inputs files to some examples: mini_c mini_xml* For example, mini_xml1.cpp contains: -{--cut here-- int main(int argc, char **argv) { char const* filename; if (argc > 1) { filename = argv[1]; } else { std::cerr << "Error: No input file provided." << std::endl; return 1; } std::ifstream in(filename, std::ios_base::in); if (!in) { std::cerr << "Error: Could not open input file: " << filename << std::endl; return 1; } -{--cut here-- However, the Jamfile doesn't show how to feed those input files to the programs. Is there some way, other than manually, to do that? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based application

Re: Rethinking the "what"

Joel de Guzman — 2008-11-23T01:49:01

That's what I did with Spirit2x. It works ok, until I had to write the expect parser where we have to supply a stream. Recall that the expectation_failure exception requires the parser to know "what" it is. There is no way in our interface to make that user configurable, unless we change the expect API into something else, which I do not want to do. No, that's a different parse tree. This is a grammar parse tree. In fact, the what function is emitting a flat version of it. In terms of complexity, it should be the same. Not sure I agree. It was never sufficient. Beyond some toy examples, it will be difficult to coax the error result into something more useful (*** but see below) Sure, that was what I planned in 2x. Alas, it's not doable unless we make expect a directive, like: p >> expect()[p2] ala classic Spirit. I don't like that. IMO, the spirit2 expect syntax is as ideal as it can be. Let's not mess with perfection ;-) I'd like to tweak something else to cater to the expect synta

Re: Rethinking the "what"

Hartmut Kaiser — 2008-11-22T15:20:18

A couple of (possibly unrelated) thought: I'ld say, make it as simple as possible and let the user supply the unknowns (like the type of the stream to use in your example above). Letting what() to create a parse tree duplicates the parse tree the user might want to create in the first place. And it adds complexity even if the user doesn't need it. The scheme we have had in Spirit2 was not ideal, but sufficient. What's perhaps missing there is the possibility for the user to customize the behavior. Creating expensive object instances during error handling is generally not an issue, at least that's the way I'm approaching error handling... Don't add more complexity to the parsing, compilation times are already scary without this. My 2€ cents. Regards Hartmut ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is

Re: Rethinking the "what"

Joel de Guzman — 2008-11-22T12:40:03

Exactly. Well, almost... Regarding pre-skipping, e will pre-skip only if it is a terminal. Perhaps it's a good idea to always do a pre-skip before throwing the exception. That way, the location of the error is dead accurate. Regards,