Re: Difficulty writing wrapper using FFI

2017-06-04 Thread Stefan_Salewski
> When I manually edited the C output to fix this, everything worked as > expected. Great. You should try to contact Araq or file a bug report to Nim issue tracker. I can remember complains about such bugs long time ago -- I assumed they were fixed already. One temporary solution may be use of

Re: Difficulty writing wrapper using FFI

2017-06-04 Thread cmacmackin
Thanks for that suggestion; I've made some progress. You were right to wonder whether it was related to passing parameters by value. It turns out that proc fprint*(value: value_t; stream: File): clonglong {.cdecl, importc: "neo4j_fprint", dynlib: libneo4j.} gets convert

Re: Nim 1.0 ?

2017-06-04 Thread opqx
Thank you.

Re: Tell Visual Studio Code to use JS backend?

2017-06-04 Thread bluenote
Ignore me: Overloading on `string` and `cstring` does not make much sense here. Problem solved by omitting the `string` version... Would still be interested in the backend config question though.

Tell Visual Studio Code to use JS backend?

2017-06-04 Thread bluenote
I'm currently experimenting with wrapping some JS test framework. A minimal example: import future proc describe(description: cstring, body: () -> void) {.importc.} proc describe(description: string, body: () -> void) = describe(description.cstring, body)

Re: Proxy difficulties

2017-06-04 Thread dom96
Ahh, looking at the headers that httpclient sends again it seems like it's buggy. The `Host` header is completely wrong. Please report this on GitHub: [https://github.com/nim-lang/Nim/issues](https://github.com/nim-lang/Nim/issues) In case you're interested in trying to fix it, here is the relev