Thanks. Would probably be the correct approach. But I tested with Nim 2.0, and
it appears to be doing this a bit different, so it seem to solve the most
difficult part for me, the type names used in inheritance.
Methods and class inheritance need runtime type information in order to
function. Maybe don't use these nim features if you don't want types in the
compiled code. Or use some sort of automated C obfuscator before calling the C
compiler (you could write some sort of shim program that obfuscates
I don't write malicious stuffs, but me too want to hide these information
There is plenty of reasons for not wanting to expose code structure, there are
also non-malicious reasons for writing obfuscated code. Stripping only removes
symbols, Nim embeds type names other places.
* Don't write malware in Nim.
* it's called stripping, there's a utility called `strip` for it
* don't write malware in Nim
Is there an option or method of compiling that does not include original
function names, class names, file names and such in the final executables? For
example, when using class inheritance the compiled file will include strings
like "someclass|somebaseclass|RootObj|" and I would prefer that
