Re:Generics in C without void* or macros – enabled by psychec
by unusualcool on Monday September 09, 2019 @12:36PM
(#20919707)
This needs to be made clearer in the readme: C++ and Haskell are requirements for building the type inference engine; Python is necessary for invoking the frontend (or the binaries can be downloaded).
Re:Generics in C without void* or macros – enabled by psychec
by Crinus on Monday September 09, 2019 @11:54AM
(#20919299)
Are you sure it isn't debugging information that bloats the executable? Try a strip --strip-all your.exe and see if it is still that big.
Re:Generics in C without void* or macros – enabled by psychec
by klingonopera on Monday September 09, 2019 @12:41PM
(#20919757)
> Try a strip and see if it is still that big.
...I guarantee that it is nothing short of humongous xD
Joking aside, maybe, I don't know, it's been a while since I used some C++ code, but I'll have a look into it the next time around.
...though it's probably unlikely, I use Code::Blocks and exclusively use the "Release" candidate, and uncheck the "Debug" version, and I'm quite confident the CB authors know what they are doing.
Re:Generics in C without void* or macros – enabled by psychec
by Crinus on Tuesday September 10, 2019 @06:26AM
(#20926701)
I do not remember Code::Blocks' configurations, but a Release configuration may still contain debug symbols so you can debug your release executable.
Re:Generics in C without void* or macros – enabled by psychec
by Gibbon1 on Monday September 09, 2019 @07:04PM
(#20923468)
> I mainly write code for embedded devices, so whatever programs I write on x86 is to interface with those devices, hence I'm quite comfortable staying with C
I'm in the same situation and I use C# for windows based tools.
One of the reasons I'm actually going for pure C in this modern day and age, is that I can just write a small program, without having any other dependency.
I'm sure the same could be said for C++, too, but for some reason, with my setup (GCC 5.1.0 with MinGW on Windows 7), I'm averaging around 800KB on C++ vs 80KB on C, for the (mostly) same code. EDIT: It appears that exception-handling is one of the reasons the binary is bigger in C++ than C.
I mainly write code for embedded devices, so whatever programs I write on x86 is to interface with those devices, hence I'm quite comfortable staying with C.