Video

"then right click inside the folder" WICH FUCKING FOLDER DUDE 😭😭(edit: nvm im stupid)

BGFX template would be godsent tbh

this tut not it gng the map doesn't even load and i did all of your steps multiple times

Rambling, can't understand what you are saying . Terrible

THANK YOU SO MUCH FOR THIS

I agree, C approaches are more effective than C++. Because, C is simple. It's time to grow over OOP bigotry. Thank you for your honesty.

Coming from C, my hatred for C++ grew day by day.

we loop over the counter 10 times

My comments discuss only the most profound mysteries of the universe and are not concerned by such lowly things as code

Procedural or Functional or a mix of the two is the way to go. SAY NO TO OOP

TBF, that's what exceptions are supposed to be for, so I always make my own assert macro wrapper over a throw, bundling some program state with the exception to make debuging easier

"If your code needs comments, probably you should improve it" -some smart guy

what kind of a programmer doesn't know asserts

Jonathan Blow does not hate comments. In fact he writes pretty long and detailed blocks of comments in his code. This video is pretty informative, but that bit is just not true.

Static assert only can use constexpr capable functions in it

So basically you still write C, but you occasionally make use of some of C++'s good features. Hopefully the container conversation was just an example and you make use of std::vector instead. Although I take issue with much of C++'s design, I do understand the reason for a lot of it. This is a huge part of why I still haven't released my own language, because a lot of the solutions I've come up with in mitigating what I consider design flaws in C++ just make things equally as awkward in my own language but in a different direction. The semantics around r-value and l-value assignments is so annoying that I'm constantly looking it up to ensure I make the right decision. And I've been using C++ since before the 98 standard came about.

asserts are really good for catching bugs as close as possible to the origin

Today, I have too much cpped

Start using Rust in your code to ×2.3 its quality!

Lol I was just about to look this up

Vă mulțumesc pentru video! (Româna mea nu este perfectă pentru că sunt ucraineancă, dar cred că ar trebui să vă mulțumesc)

-fsanitize=address

any property testing is always appreciated. I did write a simple cache and averaged an assert every two function. My test compiled at first (cpp) but didn't pass any test because of my asserts. After I finished all tests passed with correct output. It is alot easier to fix an error that failed on an assert than an error in the output and in case of a cache I would have had to step on each state and check by hand

Dude I'm in love with your content

asserts are also good for avoiding if else blocks when checking for NULL

I didn't know C++ had an assert function, thank you!

I will use my last 400 megabytes of mobile data to watch this video

I recently (a few months ago) started using asserts constantly. Especially with Python, because the lack of strict typing would make me lose my mind otherwise lol

How old are you?

Maybe some code review videos? 🤫

i have a question, for code in C++, which better? windows or linux?

yeah asserts are just good practice in general i use them in lua, really helps when you accidentally insert a parameter different than it should be and dont realize it

This channel is the only thing that makes making your own game engine possible, thank you for vids like these

What happened to your devlogs?

ive started using asserts too recently, pretty useful stuff

What are you?

please never change your accent its so iconic lmao <3

Cmakemakemakemakemake

keep going❤

No offence, but your argumets seem to boil down to "I cant be bothered to learn how a langauge feature works so therefore its bad and you'd rather makeshift one yourself", due to the lack of fundamental c++ knowledge. You first demonstrate how you dont really understand the benefits of using constructor/destructor pairs only to then turn around and make your own factory methods create() and free() (not even static methods mind you, do you make an 0-inited object first and then remember to call create() on the instance?) Then because of the lack of knowledge about them, you dont really get what a move constructor and move assignment operators are and what their intent is, while simoultaniously using placement new as an example of suboptimal performance, when in reality the perfectly forwarded version is just a micro-optimization that will mostly benefit PODs or variables known at compile time. So, a huge miss once again. The next bug in your vector also seems to stem from not understanding the lifetime rules of an object. You just cant memcpy() classes and expect it to work - we have copy constructors for that (or in your case move ctors would be more fitting). When you memcpy an object it just copies bytes as is, so a class that's designed to work as an encapsulated entity just loses all the guarantees, and I bet you run into issues only for classes with custom destructor. Btw, you can specialize your functions for data that is trivially copyable, in which case memcpy approach will not lead to errors. Naturally, your lack of exception handling is expected at this point. Its subjective, but I find exceptions a better and more encompasing mechanism than error codes and constant checking if something has gone wrong. I suspect your code mostly consists of error checking (mine was, when I first started programming in C). Similarly your distate for events seems to have the same idea behind it: constant checking seems easier than reacting to a change if it happened to happen. That's a lot of unnecessary checking, just like with error codes, but thankfully contemporary PCs can handle a few millions checks every simulation tick (read: rendered frame). To summarize: you're trying to marry C and C++ worlds (malloc vs new) world together. You can only do that if you're proficient enough in both, yet you seem to lack fundamental understanding of the very core C++ features and concepts. I suggest you actually attempt to learn C++ from a beginner level no matter how many years of experience you have writing "C with vectors" as you do now.

Some would try Godot because it's free and open-source and can be adapted to your workflow by changing how it functions as a game engine, which I think is cool that you can reuse the base of Godot and then add your own implementations to it as needed.

7:21 this is not good advice, if it takes long for your program to do deallocations, simply hide your window to do it. It won't get in the user's way and you'll also be 100% sure that no resources were leaked

what if you have a function that returns int how do you check for error code?

Amongus!

I like this. I have my own style not using all modern fancy features. I often think of it as "C+". Well, I do like constructors and destructors allocating/deallocating things if needed. I got tired of C++ standards adding more and more complexity, headers containing thousands of lines of convoluted code for things like basic vectors and strings.

btw, all those functions were from your cmake github folder? well done. You used powershell scripting under the hood? Cause I ain't gonna look

i am running it but it says stddef not such file or directory

Names are still mangled in debugger. If writing like C, might as well use C and make debugging easier.

hehe, that's how i describe my style, but i think maybe to you it would be like BASIC. all that address stuff can just be typed in place with more characters. background in audio dsp on venerable boxes, it's only gonna cut it if it's the fastest it can be. i used to have a little meter and there was about 0.08% cpu difference between a float add and mult, and that taught me everything i ever want to be aware of.

Amogus