Mirror of forum.nim-lang.org

4564 :: the ignoring of _ make some translation need more work

• oyster (orginal) [2019-01-16T14:24:53+01:00] view original

  Couldn't render post #28583.

---

• SolitudeSF (orginal) [2019-01-16T15:10:59+01:00] view original

  according to style guide, types should have uppercase first letter, and proc - lowercase. thats enough to resolve this naming conflict.

---

• Araq (orginal) [2019-01-16T17:42:08+01:00] view original

  Wrapping is always some effort, especially if you want the result to read like Nim code.

  • You need to figure out if T* means "pointer to T" or "pointer to an array of T".
  • You need to figure out how to translate #define.
  • You need to figure out if char means byte or char. Etc.

  I've wrapped hundreds of thousands of lines of C and C++ code. The underscores were the least of my worries. ;-)

---

• moerm (orginal) [2019-01-17T08:32:46+01:00] view original

  The following does work:

  // file ccall.c
  int some_weirdly_named_func(int p)
  {
     return(p += 10);
  }
  Run

  # file ccaller.nim
  {.compile:"ccall.c".}
  
  proc weirdCcall(p: cint) : cint         {.importc:"some_weirdly_named_func".}
  
  let r = weirdCcall(3)
  echo $r
  Run

  Note that nim can import "some_weirdly_named_func()" as one is free to name it in Nim as one wishes (in the example weirdCcall). One might as well stick with some_weirdly_named_func but then Nim will treat the Nim version as if one had called it someweirdlynamedfunc - but still call the correct C function.

---