You should use the .hpp extension instead of the .h when dealing with C++ code, because the modern compiler might behave differently. There is also a good hot take from Jason Turner related to it
@@mazazaza11 It doesn't have to be x86/64, learning assembly on old 8/16-bit machines where every byte and cpu cycle matters, and you can have the entire memory map for your program in your head, can really help you improve how you look after resources on modern machines. I can't believe sometimes how I can press a button on a desktop or mobile app, maybe even one I've written myself using some sort of SDK or framework, and it can be a second or more before anything actually happens, while I can write a C64 program that does the same thing within a couple of frames and feels far more snappy on a 1Mhz processor.
Sad I missed the steam, going to have to add this to my watch list for sure.
Brilliant project ! Are you planning to implement some c++ modules ? I curious to see a real life use case.
I've been going back on forth on this in my mind, as I'm not making a library I'm not sure how much sense that makes. So I guess the answer is, maybe?
You should use the .hpp extension instead of the .h when dealing with C++ code, because the modern compiler might behave differently. There is also a good hot take from Jason Turner related to it
there is also .hh and .cc which i use i think its more common in open source projects on linux
Start with assembly or C to learn how to manage resources first, then move on to higher level languages with that understanding and knowledge.
no.. not assembly but c definitely
@@mazazaza11 It doesn't have to be x86/64, learning assembly on old 8/16-bit machines where every byte and cpu cycle matters, and you can have the entire memory map for your program in your head, can really help you improve how you look after resources on modern machines.
I can't believe sometimes how I can press a button on a desktop or mobile app, maybe even one I've written myself using some sort of SDK or framework, and it can be a second or more before anything actually happens, while I can write a C64 program that does the same thing within a couple of frames and feels far more snappy on a 1Mhz processor.
@arlasoft the comment mean it as a first language but i get your point, personally i like ARM and RISCV assembly the most