From my understanding, the disadvantages would be requirement of distributing precompiled shared libraries (so the host system could work without build tools; assuming tcc or αpε is not used instead). Other disadvantages would be the lack of namespaces, and types not being as complete as they are in other languages like FORTRAN and ASN.1.
But it would be far more portable to target C than any other language, right?
(yes yes I know some of the languages that can be targeted with Kaitai [Nim] can produce C code;)
So maybe it's more of a future request, extending the Nim target to create:
wrappable C libraries
FFI access code (generated automatically) in dozens of programming languages
release these to their respective app stores (pip install, cargo install, &etc.)
From my understanding, the disadvantages would be requirement of distributing precompiled shared libraries (so the host system could work without build tools; assuming tcc or αpε is not used instead). Other disadvantages would be the lack of namespaces, and types not being as complete as they are in other languages like FORTRAN and ASN.1.
But it would be far more portable to target C than any other language, right?
(yes yes I know some of the languages that can be targeted with Kaitai [Nim] can produce C code;)
So maybe it's more of a future request, extending the Nim target to create:
pip install
,cargo install
, &etc.)Thoughts?