[Mono-bugs] [Bug 75158][Min] Changed - Socket.Connect: wrong error reported for incompatible address

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75158

--- shadow/75158	2005-06-04 18:14:58.000000000 -0400
+++ shadow/75158.tmp.11098	2005-06-05 00:15:28.000000000 -0400
@@ -1,17 +1,17 @@
 Bug#: 75158
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
-Priority: Normal
+Severity: Unknown
+Priority: Minor
 Component: System
-AssignedTo: mono-bugs at ximian.com                            
+AssignedTo: dick at ximian.com                            
 ReportedBy: gert.driesen at pandora.be               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
 Summary: Socket.Connect: wrong error reported for incompatible address
@@ -19,6 +19,11 @@
 When an incompatible address is specified (eg. IPv6 for IP protocol), 
 then Mono reports error 10049 (requested address is not valid in this 
 context) while it should in fact report error 10022 in 1.0 profile and 
 10047 in 2.0 profile.
 
 I'll commit an ignored test in SocketTest.cs to svn.
+
+------- Additional Comments From gonzalo at ximian.com  2005-06-05 00:15 -------
+I think we cannot track 'subtle' differences in the underlying socket
+implementation for every platform we support when returning an error
+in errno. I would close this as WONTFIX, Dick?