> On Jan. 27, 2015, 12:58 a.m., Joris Van Remoortere wrote:
> > 3rdparty/libprocess/3rdparty/stout/include/stout/net.hpp, line 397
> > <https://reviews.apache.org/r/29288/diff/9/?file=834346#file834346line397>
> >
> >     Here and below:
> >     Is the initialization of the members in the constructor scope a style 
> > choice here for clarity? Why initialize family in the initializer list for 
> > the default constructor, but not for the other constructors?

no, sorry for that.


> On Jan. 27, 2015, 12:58 a.m., Joris Van Remoortere wrote:
> > 3rdparty/libprocess/3rdparty/stout/include/stout/net.hpp, line 514
> > <https://reviews.apache.org/r/29288/diff/9/?file=834346#file834346line514>
> >
> >     I'm sorry if I missed something earlier, why is this not being passed 
> > by constant reference? Same for the function below.

sorry for that.


> On Jan. 27, 2015, 12:58 a.m., Joris Van Remoortere wrote:
> > 3rdparty/libprocess/3rdparty/stout/include/stout/net.hpp, lines 520-524
> > <https://reviews.apache.org/r/29288/diff/9/?file=834346#file834346line520>
> >
> >     If you provide a name for this union, then everywhere that you memset / 
> > memcpy and take sizeof(in6Addr_), as well as everywhere that you take the 
> > address of it, you can replace these with the name of the union.
> >     
> >     This is more resilient to change, and removes the implicit knowledge 
> > that we're picking on this element in the union because we know it to be 
> > the largest one.

named it InternetAddressStorage.


- Evelina


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/29288/#review69713
-----------------------------------------------------------


On Jan. 27, 2015, 4:58 p.m., Evelina Dumitrescu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/29288/
> -----------------------------------------------------------
> 
> (Updated Jan. 27, 2015, 4:58 p.m.)
> 
> 
> Review request for mesos, Benjamin Hindman, Dominic Hamon, Jie Yu, Joris Van 
> Remoortere, and Niklas Nielsen.
> 
> 
> Bugs: MESOS-1919
>     https://issues.apache.org/jira/browse/MESOS-1919
> 
> 
> Repository: mesos-git
> 
> 
> Description
> -------
> 
> Created the inner class InAddrStorage encapsulated inside the IP class.
> The class uses a union with the in_addr and in6_addr fields.
> I considered that the The MasterInfo protobuffers should have both an ipv4 
> and an ipv6 field.
> I intend to use the same Classifiers, addition, removal and update of 
> container filters, but write different encode/decode functions for IPv4/ICMP 
> and IPv6/ICMPv6 because the processing of the protocol headers differ.
> 
> 
> Diffs
> -----
> 
>   3rdparty/libprocess/3rdparty/stout/include/stout/net.hpp 
> a0210ea6440086246aafe632f86498abbb70719a 
>   3rdparty/libprocess/3rdparty/stout/tests/net_tests.cpp 
> 425132e5d7c3770be4a5a39feea5a2f22179b871 
> 
> Diff: https://reviews.apache.org/r/29288/diff/
> 
> 
> Testing
> -------
> 
> make check
> 
> 
> Thanks,
> 
> Evelina Dumitrescu
> 
>

Reply via email to