Re: Phoenix compilation problem, help?

Brett Gmoser wrote:
> Joel,
> 
> I've attached a small sample to this e-mail.  I couldn't actually 

By small, I was hoping for a few lines of code like the
one I posted here:

     http://www.nabble.com/Support-Policy-td21433231.html#a21433231

That code (posted by Peter Simmons) exemplifies what I mean by
as simple as possible. I know it takes more effort on your part,
but believe me, by isolating the exact problem that way, you'll
have a better understanding of the problem. Also, and more
importantly, people here who want to provide you with support
will spend less time analyzing the code.

> replicate the exact problems I was having entirely (there's another odd 
> error in the attachment that doesn't happen on my full version), but the 
> problem itself is still there.  While I was at it, I had a few more 
> bind-related questions, I hope nobody minds me including those as well 
> so I can figure out what I am doing wrong.  

I suggest breaking it up and putting it in another post.

Regards,
--

-- 
Joel de Guzman
http://www.boostpro.com
http://spirit.sf.net

Re: Phoenix compilation problem, help?

Joel,

I absolutely respect the value of your time and the others reading this 
list, it is certainly (and I truly mean this as a compliment) much more 
valuable than mine (especially in the case of yours specifically).  I am 
sorry the code sample isn't to your specifications.

However with all due respect, I did actually spend the better part of a 
full work day "crobaring" out portions of my very large project, down to 
just the smallest bits possible to demonstrate the problems I am 
having.  I certainly *have* gained a better understanding of the 
problem, and it was a good exercise, but I still can't figure out what I 
want to do.  Being code written for Spirit 1.8.x, it is a little more 
verbose than what would have been written for use with Spirit 2, but it 
consists only of the following:

  - A grammar, with a single rule (expression), plus an additional 
"starting" rule because I wasn't able to compile the code without that.  
The single rule has a few semantic actions attached to it, but they are 
all there to demonstrate three very specific problems that I am having.
  - A single closure, with some extra verbosity to support GCC.  Would 
not be necessary for Spirit 2, but it is necessary for Spirit 1.8.x.
  - A single Phoenix function, necessary to demonstrate one of the three 
problems at hand.
  - A typedef for a boost.variant, I left out most of the other 6 or so 
types, leaving just enough to demonstrate what's going on.  It's 
necessary to include the variant code, because that is a major part of 
my problem - using the "deferred visitation" functor returned by 
boost::apply_visitor.  I could possibly replicate this using my own 
functor, but not knowing anything about variant internals I'm not sure I 

Re: Phoenix compilation problem, help?

Brett Gmoser wrote:
> Joel,
> 
> I absolutely respect the value of your time and the others reading this 
> list, it is certainly (and I truly mean this as a compliment) much more 
> valuable than mine (especially in the case of yours specifically).  I am 
> sorry the code sample isn't to your specifications.
> 
> However with all due respect, I did actually spend the better part of a 
> full work day "crobaring" out portions of my very large project, down to 
> just the smallest bits possible to demonstrate the problems I am 
> having.  

Ok, understood. I'll have a look at it then. Pardon me for being lazy :-P

Regards,
--

-- 
Joel de Guzman
http://www.boostpro.com
http://spirit.sf.net

------------------------------------------------------------------------------

Re: Phoenix compilation problem, help?

On Mar 31, 2009, at 10:34 PM, Joel de Guzman wrote:

> Brett Gmoser wrote:
>> Joel,
>>
>> I absolutely respect the value of your time and the others reading  
>> this
>> list, it is certainly (and I truly mean this as a compliment) much  
>> more
>> valuable than mine (especially in the case of yours specifically).   
>> I am
>> sorry the code sample isn't to your specifications.
>>
>> However with all due respect, I did actually spend the better part  
>> of a
>> full work day "crobaring" out portions of my very large project,  
>> down to
>> just the smallest bits possible to demonstrate the problems I am
>> having.
>
> Ok, understood. I'll have a look at it then. Pardon me for being  
> lazy :-P

   Looks confusing to me:)

------------------------------------------------------------------------------

[phoenix2] find

------------------------------------------------------------------------------

_______________________________________________
Spirit-general mailing list
Spirit-general <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spirit-general

Re: [phoenix2] find

Sergei Politov wrote:
> Hi
> 
>   There is two variants of find in stl - as algorithm, and as method of 
> associative containers.
>   When using boost::phoenix::find it tries to detect automatically which 
> kind is used.
>   When user tries to use it with associative container it fails to 
> detect non stl containers.
>   As can be seen from comment:
>     // Specialize this for user-defined types
>   It is supposed to make it manually. But there is a lot of containers 
> in boost, that supports find.
> 
>   I suggest to add boost::phoenix::container_find functor that forces to 
> use find method.
>   Also there are other functors that could be added in the same way - 
> lower_bound, upper_bound etc.
>   Moreover it would be cool to add boost containers to auto detection.
> 
>   I think that I could prepare patсh, if someone interested.

I'm interested.

Regards,
--

-- 
Joel de Guzman
http://www.boostpro.com
http://spirit.sf.net

------------------------------------------------------------------------------
_______________________________________________
Spirit-general mailing list
Spirit-general <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spirit-general

[Spiriti2x] Use of my own types inside semantic action

Hi,

is it possible to use my own types inside of semantic actions without to 
use Boost::Fusion or Boost::Variant? Cause my types are more "complex" 
unlike a tuble/vector or a field with variable types. I want to to 
something like this:
===========================
.. [_val(_r1)];   // we assume _val represent an object of my types and 
i hope its possible to create a new one like this :)
.. [_val.set_name(_r1)];
===========================
_val and _r1 are the arg_names of spirit. set_name should represent a 
function from a type of mine.

Is that, or soemthing like that, possible with Spirit2x? I hope anyone 
can give me a suggestion, thank you very much in advance!

Best regards
Christian

No virus found in this outgoing message.
Checked by AVG - http://www.avg.com 
Version: 8.0.138 / Virus Database: 270.11.35/2034 - Release Date: 01.04.2009 06:06

------------------------------------------------------------------------------

Spirit 2x and Lex

Spirit 2x does not contain a Lex component. It the Spirit 2 Lex
compatible with Spirit 2x Qi?

Thanks,
Christopher Currie

------------------------------------------------------------------------------

Re: Spirit 2x and Lex

> Spirit 2x does not contain a Lex component. It the Spirit 2 Lex
> compatible with Spirit 2x Qi?

I never tried :-P 
But I assume it is. Would you be willing to try it out and report back?

Regards Hartmut

------------------------------------------------------------------------------

Re: Spirit 2x and Lex

Sure, I'll give it a try and let you know.

On Thu, Apr 2, 2009 at 1:59 PM, Hartmut Kaiser <hartmut.kaiser <at> gmail.com> wrote:
>> Spirit 2x does not contain a Lex component. It the Spirit 2 Lex
>> compatible with Spirit 2x Qi?
>
> I never tried :-P
> But I assume it is. Would you be willing to try it out and report back?
>
> Regards Hartmut
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Spirit-general mailing list
> Spirit-general <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/spirit-general
>

------------------------------------------------------------------------------