← Back to context

Comment by integricho

6 days ago

Agreed, I thought this is a wrapper for STL under Python, what does the py prefix stand for here actually?

As for the why c++ at all, as long as one falls into the "don't care" category, it works fine.. lately I found myself I rather build my apps in C with NODEFAULTLIB (under Windows at least), and creating my own size-optimized standard library which on Windows wraps the Win32 API wherever possible. The size savings are incredible, my executable is in the ~500KB range, ultra small and ultra fast. This is unattainable with normal modern C++.

12 comments

integricho

Reply
pjmlp  6 days ago

I instead, use VC++ latest with C++23 import std.

As for the size requirements, and having Windows experience all the way back to Windows 3.0, you can do exactly the same tricks with C++.

  • integricho  6 days ago

    Have you checked what dll dependencies you get if you build such an app? And have you actually tried running such an executable on win9x?

    • pjmlp  6 days ago

      If you use only Win32 APIs from C++ just like since Petzold books, the dlls are already there, there is also static linking for other stuff.

      Win 9x is a dead OS, why would I bother with that outside retro computing?

      5 replies →

dsab  6 days ago

Out of curiosity what are your projects written in C for Windows? GUI apps?

  • integricho  6 days ago

    Yes, I am building GUI apps. This "standard library" of mine is built from the ground up in a cross platform manner, such that it compiles on Windows wrapping Win32, with Windows 95 being the CI machine, making sure it works on the whole Windows family upwards, and it wraps POSIX under Linux/MacOS/any POSIX system. The goal being to reuse the available shared library dependencies that are always present on these platforms anyway, giving me these ultra small binaries.