Boost Users :

eric.malysa_at_[hidden]

-- 
------------------------------
Message: 4
Date: Tue, 06 Aug 2013 18:53:12 -0400
From: Edward Diener <eldiener_at_[hidden]>
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] Boost.Variant broke in 1.54?
Message-ID: <ktruoj$mod$1_at_[hidden]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 8/5/2013 7:47 AM, Krzysztof Czainski wrote:
> 2013/8/4 Edward Diener <eldiener_at_[hidden] 
> <mailto:eldiener_at_[hidden]>>
>
>     On 8/4/2013 8:57 AM, gast128 wrote:
>     Returning a 'const X' is meaningless. Just return 'X' instead.
>
>
> Just to clarify, Edward, I think you're wrong. Consider:
>
> struct X { void go() {} };
>
> X source_a();
> X const source_b();
>
> int main()
> {
>    source_a().go(); // ok
>    source_b().go(); // error
>
>       The same goes for passing something as 'const X'.
>
>
> I assume you mean a function *taking* something as 'const X'. Consider:
>
> void g( X x );
> void g( X const x );
>
> The two declarations of g() are equivalent (!), so you could say this 
> 'const' is meaningless ;-). The 'const' here matters in the 
> implementation of function g.
>
> void f( X x, X const y )
> {
>    x.go(); // ok
>    y.go(); // error
>
>     When you pass or return by value you get a copy of the object being
>     passed so it means nothing to say that the object is 'const'.
>
>
> Considering what I've written above, I disagree that 'const' means 
> nothing here. When function source_b() returns by const value, it
> *means* the returned temporary is const. When function f() takes by 
> const value, it *means* the implementation of f() doesn't modify the 
> copy it gets. For the caller of f(), this 'const' is meaningless 
> indeed ;-)
I am aware of the syntax and its meaning. I specified "meaningless" not because the syntax is meaningless ( if it was the compiler would issue an error about the syntax itself ) but because the practical use of specifying 'const' in either situation is meaningless IMO. You are getting a copy of some X. Why would you practically specify that this copied value cannot be changed ? I do not see a practical programming reason for doing anything that way despite your correctly formed examples above.
My reply was abrupt in that I should have specified as a suggestion that the 'const' just be dropped to solve the practical problem, not that the problem did not exist.
------------------------------
Message: 5
Date: Wed, 7 Aug 2013 13:11:41 +0300
From: Igor R <boost.lists_at_[hidden]>
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] Library Status
Message-ID:
	<CAPnv1PKZsOthwmR1JB=5vPjMFW+N=Gvrw0=O2EpSzzyxS8RAaw_at_[hidden]>
Content-Type: text/plain; charset=UTF-8
> What conditions for a "bin" directory is library_status.cpp looking 
> for? The documentation seems either inadequate or wrong.
>
> I am getting an error:
>
> **** exception(205): std::string: invalid bin directory structure
>
> ******** errors detected; see standard output for details ******** I 
> am using compiler gcc 4.3
Could you be more specific? What are you doeing exactly, on what platform, what's boost version etc?
------------------------------
Message: 6
Date: Wed, 07 Aug 2013 14:41:53 +0400
From: Alexander Mingalev <infest21h_at_[hidden]>
To: boost-users_at_[hidden]
Subject: [Boost-users] [msm] exit points & favor compile time policy
Message-ID: <52022471.4020207_at_[hidden]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Hi,
I faced to a strange problem. I'm working with root fsm & child fsm. 
Child fsm has an exit point called "End".
I use vs2012u3, boost 1.54
transition table from root looks like that:
struct Waiting : state<> {};
// Child is typedef for back-end
struct transition_table : public boost::mpl::vector< ...
Row < Waiting, begin, Child >,
Row < Child::exit_pt<Child::End>, none, Waiting >, ...
 > {};
So, when I use F-C-T- policy, the Child fsm is stuck in Child::End state, the root fsm never moves to Waiting again.
It doesn't happen with default policy.
I noticed, that there is a note in msm's changelog  From V2.24 to V2.25 (Boost 1.54) ? Bugfix: Exit points broken for the favor_compile_time policy.
looks similar to my case.
Christophe, can you check that bugfix?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4916 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.boost.org/boost-users/attachments/20130807/0307c126/attachment.bin>
------------------------------
Message: 7
Date: Wed, 7 Aug 2013 15:49:45 +0400
From: Antony Polukhin <antoshkka_at_[hidden]>
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] cannot use boost asio 1.54 with visual
	studio 2008
Message-ID:
	<CAKqmYPYWG=ME969ZQbQ0Etn4p3OrQ0_yKK=HAK+hr9Gyoh1TRA_at_[hidden]>
Content-Type: text/plain; charset="iso-8859-1"
2013/8/6 bnsteel <bnsteel_at_[hidden]>
> I mean *1.54!!*
>
Please explain in more details. At least show the error messages.
--
Best regards,
Antony Polukhin
-------------- next part --------------
HTML attachment scrubbed and removed
------------------------------
Subject: Digest Footer
_______________________________________________
Boost-users mailing list
Boost-users_at_[hidden]
http://lists.boost.org/mailman/listinfo.cgi/boost-users
------------------------------
End of Boost-users Digest, Vol 3529, Issue 1
********************************************