hcorion, its a workaround. You need to create context via
proc newContext*(protVersion = protSSLv23, verifyMode = CVerifyPeer,
certFile = "", keyFile = "", cipherList = "ALL"):
SSLContext =
You can find this function in net.nim
[[https://github.com/nim-la
**pipes** \- OS specific pipes, for Posix systems this is
[https://linux.die.net/man/3/pipe](https://linux.die.net/man/3/pipe). For
Windows this called Named Pipes
[https://msdn.microsoft.com/en-us/library/windows/desktop/aa365590(v=vs.85).aspx](https://msdn.microsoft.com/en-us/library/windows/d
Also you need to know that nanomsg is a wrapper library, so you need to handle
nanomsg shared library itself.
god, if you dont care about speed, you can use any library you can find in
nimble which uses sockets underneath. But sockets are not native mechanism for
any OS for inter-process communication, so there can be many troubles (like not
properly closed ports, timeouts, etc). So its better and safer
You can use this
[https://github.com/cheatfate/asynctools/blob/master/asynctools/asyncipc.nim](https://github.com/cheatfate/asynctools/blob/master/asynctools/asyncipc.nim)
if async is not a problem for you.
You must not using signed integers in pointer arithmetic, just because memory
address can't be negative and can be higher, then **0x8000_** for 32 bit
platforms and **0x8000___** for 64 bit platforms. So
var newp = cast[pointer](cast[uint](oldp) + 1u)
@vega, answer to your second question is
[https://github.com/nim-lang/Nim/pull/4680](https://github.com/nim-lang/Nim/pull/4680)
