Mirror of forum.nim-lang.org

4690 :: nlvm update

• arnetheduck (orginal) [2019-03-04T05:22:49+01:00] view original

  Couldn't render post #29258.

---

• Araq (orginal) [2019-03-04T08:07:12+01:00] view original

  Well there is

  const
    NimCompilerApiVersion* = 3 ## Check for the existance of this before accessing it
                               ## as older versions of the compiler API do not
                               ## declare this.
  Run

  in compiler/nversion.nim

---

• arnetheduck (orginal) [2019-03-04T16:17:14+01:00] view original

  lol wish it were that easy ;) for someone consuming the compiler it might, actually, but..

---

• cdome (orginal) [2019-03-06T11:42:09+01:00] view original

  @arnetheduck Very interesting, I will try to play with this backend. I am quite heavy user of importcpp and header pragmas hence unlikely will be able to use it in projects, however not every module depends on cpp imports. It would be interesting to be able to mix/match modules compiled with standard cpp backend and modules compiles with llvm native backend. Do you think it is feasible?

---

• arnetheduck (orginal) [2019-03-07T20:06:28+01:00] view original

  Do you think it is feasible?

  probably not. what would likely be needed is that nim would expose a nim api/abi to nlvm, much like if you had wrapped a c++ library with a c api.. that would require a lot of changes to nim, including specifying an ABI etc.

  header pragmas for C stuff are kind of not needed if you take care to correctly specify the ABI (correct function signatures / types) - that's how nlvm is able to use the nim std lib which is full of references to the C std library. In fact, nim itself doesn't really need header if you write things correctly. Of course, for C++ that's nearly impossible.

---