Re: [Boost-users] Boost-users Digest, Vol 3288, Issue 1

5 Dec 2012

      Hi,

 Could you try it with MS compiler and any release prior to the 1.52.0?

-----Original Message-----
From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of boost-users-request@lists.boost.org
Sent: 04 December 2012 17:29
To: boost-users@lists.boost.org
Subject: Boost-users Digest, Vol 3288, Issue 1

Send Boost-users mailing list submissions to
	boost-users@lists.boost.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.boost.org/mailman/listinfo.cgi/boost-users
or, via email, send a message with subject or body 'help' to
	boost-users-request@lists.boost.org

You can reach the person managing the list at
	boost-users-owner@lists.boost.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost-users digest..."

Today's Topics:

   1. Re: Boost 1.49.0 compilation issue (Marshall Clow)
   2. Re: boost msm - Multiple differed events (Kamel Zaarouri, Mr)
   3. [serialization] versioning for class nested within	template
      class (Gabriel Redner)
   4. Re: Asio and software interrupts (Steve Lorimer)
   5. Spirit guidance needed (Arkadiy and Marina Vertleyb)
   6. [boost][polygon]Errors with minkowski sum (renaud lepere)
   7. Re: Spirit guidance needed (Igor R)
   8. Experience with dealing with warnings from the Clang	toolset?
      (Paul A. Bristow)

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

Message: 1
Date: Mon, 3 Dec 2012 09:29:59 -0800
From: Marshall Clow 
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] Boost 1.49.0 compilation issue
Message-ID: 
Content-Type: text/plain; charset=us-ascii

On Dec 2, 2012, at 1:47 AM, Shcherbina Vladimir  wrote:
...
I tried to compile this boost dependent class with VS2008 and VS2010 
(error lines are in bold)
Another data point:
	I was able to successfully compile your code with clang. and the 1.52.0 release.

-- Marshall

Marshall Clow     Idio Software   mailto:mclow.lists@gmail.com

A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait).
        -- Yu Suzuki

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

Message: 2
Date: Mon, 3 Dec 2012 21:08:57 +0000
From: "Kamel Zaarouri, Mr" 
To: "boost-users@lists.boost.org" 
Subject: Re: [Boost-users] boost msm - Multiple differed events
Message-ID:

Content-Type: text/plain; charset="us-ascii"

Hi Guys,

Let's say that we have 2 states, S1 and S2. 
with this transition table:

S1 -> S2 on event Es2
S2 -> S1 on event Es1

also let's say that S1 can also accept Ev1 and Ev2 but S2 cannot accept them so it differs them.

Now when let's say that S2 receives 2 events Ev1 and Ev2 and differs them. Now, when S2 goes back to S1 would S1 handle both events in order? or how does it work?

Thanks,

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

Message: 3
Date: Mon, 3 Dec 2012 17:51:40 -0500
From: Gabriel Redner 
To: boost-users 
Subject: [Boost-users] [serialization] versioning for class nested
	within	template class
Message-ID:

Content-Type: text/plain; charset=windows-1252

Hi folks,

I am having trouble incrementing the serialization version of a regular class nested within a template class.  I'm not sure if the problem is with boost or with my own understanding of the issue.

My code looks like:
==============================
template 
struct Foo
{
  struct Bar
  {
    int data1;
    int data2;

  private:
    friend class boost::serialization::access;
    template<class Archive>
    void serialize(Archive & ar, unsigned int version)
    {
      ar & data1;
      if (version >= 2) {
        ar & data2;
      } else {
        data2 = 0;
      }
    }
  };
};
==============================

My attempt at setting the version looks like:
==============================
namespace boost {
namespace serialization {

template 
struct version::Bar>
{
  BOOST_STATIC_CONSTANT(unsigned int, value = 2); };

} // namespace serialization
} // namespace boost
==============================

However, g++ gives an error:
==============================
main.cpp:31:8: error: template parameters not used in partial specialization:
main.cpp:31:8: error:         ?A?
main.cpp:31:8: error:         ?B?
==============================

Strangely, clang 3.0 compiles the code but issues some warnings:
==============================
main.cpp:31:8: warning: class template partial specialization contains template parameters that can not be deduced;
      this partial specialization will never be used struct version::Bar>
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
main.cpp:30:20: note: non-deducible template parameter 'A'
template 
                   ^
main.cpp:30:32: note: non-deducible template parameter 'B'
template 
                               ^
1 warning generated.
==============================

I'd appreciate any pointers!

Thanks,
-Gabe

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

Message: 4
Date: Tue, 4 Dec 2012 10:17:33 +1100
From: Steve Lorimer 
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] Asio and software interrupts
Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

On 4 December 2012 01:51, Joseph Sulewski  wrote:
...
*When I call socket->bind I provide it with an endpoint.  When I 
create the endpoint I'm currently using the multicast address, what 
should I use for the address?  *
If you bind to INADDR_ANY then the OS will use its ip routing tables to work out which the best local nic to use is. You can force it to use a specific local nic by providing its address. Most applications will use INADDR_ANY

*If I'm binding to multiple multicast addresses it doesn't make sense to
...
bind to one of them.*
Because UDP is connectionless there is no way for the kernel / network stack to know which pid to deliver datagrams to for a particular port unless you bind your socket's file descriptor to that port.
(note, if you want to allow other file descriptors to be able to bind to that port you need to set SO_REUSEADDR to 1)
...
*Finally,  it appears I can join multiple multicast groups but they 
need to be the same port.  Is this correct?*
The reason for this is as my previous point above. What you would do is create as many sockets as there are different ports, and have each socket join the multicast addresses which are on that port
...