RE: [boost] Re: sockets Interface for address class

From: Iain.Hanson_at_[hidden]
Date: 2002-03-01 10:51:07

     Sorry, I sent this privately when I meant to send it to the list.
     
     /ikh

______________________________ Forward Header __________________________________
Subject: RE: [boost] Re: sockets Interface for address class
Author:  Iain Hanson at ln,c,london,it
Date:    01/03/02 14:51

     
I think I was suffering from brain fade. I've removed the explicit and I'll 
update the interface in the files  socket2/address.html
     
/ikh
     
______________________________ Reply Separator _________________________________
Subject: RE: [boost] Re: sockets Interface for address class
Author:  jonkalb (jonkalb_at_[hidden]) at unix,mime 
Date:    28/02/02 21:41
     
     
I think I must be missing something.
     
It is my understanding that the explicit keyword prevents the 
constructor from being used as a conversion operator which would, in 
this case, allow any string to be implicitly converted into an address. 
     
Since a two parameter constructor cannot be used as a conversion 
operator, I don't see why any such constructor would be designated 
explicit.
     
Are you saying that the explicit keyword has some effect on how 
parameters to the constructor are treated?
     
     
-----Original Message-----
From: Iain.Hanson_at_[hidden] [mailto:Iain.Hanson_at_[hidden]] 
Sent: Thursday, February 28, 2002 12:05 PM
To: boost_at_[hidden]
Subject: RE: [boost] Re: sockets Interface for address class
     
     
In order to prevent char * being converted to std::string unnecessarily. 
I was 
not 100% sure that const char * version would be prefered over 
conversion to 
Sstd::string.
     
/ikh
     
______________________________ Reply Separator 
_________________________________
Subject: RE: [boost] Re: sockets Interface for address class 
Author:  jonkalb (jonkalb_at_[hidden]) at unix,mime
Date:    28/02/02 19:51
     
     
Why is this two parameter constructor explicit?
     
-----Original Message-----
From: Iain.Hanson_at_[hidden] [mailto:Iain.Hanson_at_[hidden]] 
Sent: Thursday, February 28, 2002 7:37 AM
To: boost_at_[hidden]
Subject: Re: [boost] Re: sockets Interface for address class
     
     
  explicit address ( const std::string & Address , port_type Port );
     
     
     
Info: http://www.boost.org  Send unsubscribe requests to: 
<mailto:boost-unsubscr
ibe_at_[hidden]> 
     
Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/ 
     
     
     
     
Visit our website at http://www.ubswarburg.com
     
This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.
     
E-mail transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive 
late or incomplete, or contain viruses.  The sender therefore does not 
accept liability for any errors or omissions in the contents of this 
message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.
     
     
Info: http://www.boost.org  Send unsubscribe requests to: 
<mailto:boost-unsubscribe_at_[hidden]> 
     
Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/ 
     
     



Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.