theICEBeardk

5 ms·

1.
by theICEBeardk 4mo ago
Yeah I remember doing that in one project. And then at least I found c++ and ATL back when it came out. I never went back to doing COM in C after that.
2.
by theICEBeardk 4mo ago
I mean a readable implementation of tuple with minimal overhead is a great case for me (went from around 1.6k lines to approximately 250 lines). I wrote an implementation including the normally difficult to implement tuple_cat based on c++2
3.
by theICEBeardk 4mo ago
The answer is being debated at the moment in c++ papers and building on experience from other languages with extensive compile time evaluators like D. One thing that is happening is that we will get compile time exceptions (a paper for that
4.
by theICEBeardk 4mo ago
We love-hate you and the Norwegian Fjellaber as well, you Swedish drunkard. A Dane.
5.
by theICEBeardk 6mo ago
While this is helpful in a way this blog also contains outdated information. Given that in embedded you most of the time build the world and have most of your stuff as source code you should never get stuck on an old compiler unless it is a
6.
by theICEBeardk 8mo ago
I will be honest mentioning Zephyr in a situation when talking about how outdated the Unix design philosophy is, is a bit funny to me since Zephyr (like ecos kinda did once) tries to be Posix-like in its APIs (but ends up not really improvi
7.
by theICEBeardk 10mo ago
https://en.cppreference.com/w/cpp/freestanding.html to see the parts you can use.
8.
by theICEBeardk 10mo ago
Apparently according to some ACCU and CPPCon talks by Khalil Estel this can be largely mitigated even in embedded lowering the size cost by orders of magnitude.
9.
by theICEBeardk 10mo ago
Are you aware of the Freestanding definition of STL? See here: https://en.cppreference.com/w/cpp/freestanding.html Large and useful parts of it are available if you run with a newer c++ standard.
10.
by theICEBeardk 1y ago
No it is gaining compile time reflection. But RTTI has been a thing for a long time.
11.
by theICEBeardk 1y ago
c++ gets a lot of hate much of it based on past traumas with specific codebases and history of use. This has built up into a culture where people who have little to no experience with c++ but who have been told and seen only bad headlines a
12.
by theICEBeardk 1y ago
A lot of the stuff they are working on for c++29 is exactly what you are wishing for (me too by the way).
13.
by theICEBeardk 1y ago
Yeah no switching a group of developers over to some new language is not more efficient. It is a lot of work. And on top of that you will need to add time to either wrap your existing code base or rewrite it with developers who are new to t
14.
by theICEBeardk 1y ago
I work on a c++23 embedded platform that is used in very small microprocessors up to embedded linux stuff. We ship stuff that needs to run constant and C was just too unsafe for us (C requires you to remember to call functions RAII saves yo