nimsuggest already support this for the EPC protocol, the picked port number is
written to stdout so that the client can see it. We could provide this feature
for every protocol via `--port:auto`.
To answer my own question below is something that worked (AFAIK) - you will
have to search out the other ICC definitions.
type TINITCOMMONCONTROLSEX = object
dwSize:DWORD
dwICC:DWORD
const
ICC_UPDOWN_CLASS= 0x10
proc
Below is something that worked (AFAIK) - you will have to search out the other
ICC definitions.
type TINITCOMMONCONTROLSEX = object
dwSize:DWORD
dwICC:DWORD
const
ICC_UPDOWN_CLASS= 0x10
proc InitCommonControlsEx*(lpInitCtrls:ptr
The regression seems to appear in commit b78029b5afb3bfa69cf. (fixes #4626)
here is a testfile.
type
Element = enum
FIRST
SECOND
THIRD
converter toInt*(x: Element): int = x.int
var data = [1,2,3]
echo(data[SECOND])
In the last days I was going to spent some time debugging the random NEd Nim
editor crashes. Unfortunately, while I got some crashes some weeks ago when
working on the chess game, I was not able to generate crashes when testing. So
I think I have to wait until a real crash occurs again, and
You've come this far, can you point down the specific commit that caused it? :)
Yes, that can be confusing. In Module system.nim we have
cint* {.importc: "int", nodecl.} = int32
## This is the same as the type ``int`` in *C*.
This means that the ordinary = int32 is indeed overwritten by importc pragma.
So cint is indeed always C's int.
Just a quick question that I couldn't find the answer to anywhere. According to
the [system module
description](http://forum.nim-lang.org///nim-lang.org/docs/system.html#cint),
cint is supposed to be equivalent to using "int" in C. However, cint is
explicitly defined as int32, whereas C does
Removed the temp variable declarations in the latest check in. I'm sure there's
a better way to do the repetitive parseInts.
Looks like this now:
proc net_io_counters*(): TableRef[string, NetIO] =
## Return network I/O statistics for every network interface
##
