sockets compile again with SSL support

lib/pure/sockets.nim

@@ -1021,7 +1021,7 @@ proc recvAsync*(socket: TSocket, s: var TaintedString): bool =
     when defined(ssl):
       if socket.isSSL:
         if bytesRead <= 0:
-          var ret = SSLGetError(socket.sslHandle, bytesRead)
+          var ret = SSLGetError(socket.sslHandle, bytesRead.cint)
           case ret
           of SSL_ERROR_ZERO_RETURN:
             SSLError("TLS/SSL connection failed to initiate, socket closed prematurely.")
@@ -1088,7 +1088,7 @@ proc sendAsync*(socket: TSocket, data: string): bool =
   when defined(ssl):
     if socket.isSSL:
       if bytesSent <= 0:
-          let ret = SSLGetError(socket.sslHandle, bytesSent)
+          let ret = SSLGetError(socket.sslHandle, bytesSent.cint)
           case ret
           of SSL_ERROR_ZERO_RETURN:
             SSLError("TLS/SSL connection failed to initiate, socket closed prematurely.")

todo.txt

@@ -1,6 +1,8 @@
 version 0.9.0
 =============
 
+- change overloading resolution
+- implicit ref/ptr->var conversion
 - deprecate ``var x, y = 0`` as it's confusing for tuple consistency
 - finish support for unsigned ints:
   - support more unsigned operations
@@ -53,12 +55,9 @@ version 0.9.XX
 - make 'clamp' a magic for the range stuff
 - implement a warning message for shadowed 'result' variable
 - implement the high level optimizer
-- change overloading resolution
 - we need to support iteration of 2 different data structures in parallel
 - implement proper coroutines
-- implicit ref/ptr->var conversion; the compiler may store an object
-  implicitly on the heap for write barrier efficiency; better: 
-  proc specialization in the code gen
+- proc specialization in the code gen for write barrier specialization
 - tlastmod returns wrong results on BSD (Linux, MacOS X: works)
 - nested tuple unpacking; tuple unpacking in non-var-context
 - 'nimrod def': does not always work?