4 ms·
For embedded use it's probably ok, anywhere C is ok. It statically links the bits of the stdlib you use but dead code elimination seems to work pretty well. A
by TylerE 13y ago
For embedded use it's probably ok, anywhere C is ok. It statically links the bits of the stdlib you use but dead code elimination seems to work pretty well.
A simple word counting script I just wrote compiles down to about 52k on 64bit OS X.
(Src: https://gist.github.com/tylereaves/7711302 https://gist.github.com/tylereaves/7711302)
- progman 13y agoThanks - but your example is Python code ??
- TylerE 13y agoNo, it's Nimrod. I set it to python in gist because that's the closest to nimrod for syntax highlighting purposes. Edit: Apparenetly not...there are alot more modes in there but the UI exposing them is easy to miss
- flyinglizard 13y agoI also wonder about Nimrod on embedded. The dealbreaker is dynamic memory allocation; if Nimrod does that as a non-negotiable part of its runtime, it can't be used.
- jamesaguilar 13y agoIt looks like this might rely on the GC. From the description, you can cut that out too if you handle cleanup yourself. Not sure though.