@monster please take a look into nim's thread implementation. The nim-type
"Thread" contains the systems thread handle and so on. So I think it's a good
habit to keep this reference vital You need it also later on for cleanup. Hope
this helps you.
Anyway that error is related to the SSL protocol version the client and the
server are trying to negotiate. See
[here](http://openssl.6102.n7.nabble.com/quot-SSL3-GET-RECORD-wrong-version-number-quot-td8310.html)
for example. I think it little nothing to do with Nim SSL wrapper, you could
try t
OK, I've got it! It has _nothing_ to do with runForever() or asyncdispatch.
Here another example that crashes:
import os
proc whatever() {.thread, nimcall.} =
echo("TEST")
proc initProcessX(): void =
echo("In initProcess()")
var thread: Thread[void
skinte please use the example of the WMI.
Let's output the value of SELECT * FROM Win32_Processor (ProcessorId)
Sorry for mistakes, use google translate
Sorry to bump this thread but, the above link is expired now; where can I find
an sdl2_gfx.dll for x64 Windows? I'm having trouble building it myself and the
above link seems to be the only one on the Internet. I'm just trying to get
basic SDL stuff working in x64 Nim on Windows
> I haven't studied Haskell's solution enough to be able to answer this
> question.
lol. That's a good reason
@woggioni no, here other issue if set parameter useSsl = true in newSmtp then
error raise in net.nim
when defineSsl: #in our case true!
if socket.isSSL: #in our case true!
# RFC3546 for SNI specifies that IP addresses are not allowed.
if not isIpAddress(ad
@dom96 Thank you very much for your reply. Having an open and transparent
pathway to 1.0 is going to be so important for the community and for fostering
adoption. Thank you for all of your efforts. I just had my new Nim book arrive
in the mail this week. Can't wait to read it!
