pointer to array?

2017-05-05 Thread jxy
Hi, I'm trying to interface some C library where the library function accepts a function pointer for callbacks. proc libfun(fun:proc(x:pointer; n:ptr cint)) {.importc:"libfun", header:"mylib.h".} I'm trying to write this `fun` proc in Nim, and pass it to `libfun`. How do I t

Re: Nim - Unique Module Names

2017-05-05 Thread ivanitto
Thank you for the explanation. Yes, I'm really with you on the idea of enforcing the coding style. I'm not fully sure yet, but looks like I'm having a case where it would be better (for the sake of simpler/clearer software design) to distinguish symbols basing on the filesystem path.

Re: when will [] ambiguous be solved?

2017-05-05 Thread Krux02
Wait a moment, are you shure this D code is equivalent to the Nim code you just posted? struct Bar { void bar() { "bar".writeln; } } To me this looks like just a _method_ (in c++ terms). And a _method_ is not a value member of a struct. In other words it does not increase the

Re: when will [] ambiguous be solved?

2017-05-05 Thread Varriount
It will probably be solved: * After all other higher-priority features/bugs are solved * When someone contributes a patch that resolves the ambiguity It's not really a big problem. Just use "foo[T](42)" or "foo(42)[T]". I don't think it warrants a syntax change.