4 ms·

No void* or macros, but requires a special compiler frontend.

by TorKlingberg 7y ago

jackewiehose 7y ago
Yes, that was confusing. "Look, you don't need to use these C-features if you use another language than C."
- klingonopera 7y ago
  C++ 14, Haskell and Python. 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.
  - unusualcool 7y ago
    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).
  - Crinus 7y ago
    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.
    - klingonopera 7y ago
      > 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.
      - Crinus 7y ago
        I do not remember Code::Blocks' configurations, but a Release configuration may still contain debug symbols so you can debug your release executable.
  - Gibbon1 7y ago
    > 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.
deleted 7y ago
[deleted]
unusualcool 7y ago
Sorry, it wasn't my intention to be tricky, that's why I added "enabled by psychec" to the subject line. I hope that, once landing at the project page, it should be obvious that such functionality is provided by a tool.

No void* or macros, but requires a special compiler frontend.

jackewiehose 7y ago

Yes, that was confusing. "Look, you don't need to use these C-features if you use another language than C."

klingonopera 7y ago
C++ 14, Haskell and Python. 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.
- unusualcool 7y ago
  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).
- Crinus 7y ago
  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.
  - klingonopera 7y ago
    > 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.
    - Crinus 7y ago
      I do not remember Code::Blocks' configurations, but a Release configuration may still contain debug symbols so you can debug your release executable.
- Gibbon1 7y ago
  > 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.

deleted 7y ago

[deleted]

unusualcool 7y ago

Sorry, it wasn't my intention to be tricky, that's why I added "enabled by psychec" to the subject line. I hope that, once landing at the project page, it should be obvious that such functionality is provided by a tool.