วีดีโอ

Assembly isn't nearly as portable nor cross platform for that matter

I would say the best option is to pick a book

I rewrote my sanity in Rust after C++

m-muh memory safety!!!

Ewww

it's 2D and raylib doesn't have update and draw methods as far as i know, if you're using it you need to set the loops up yourself. correct me if i'm wrong

1. i recommend "the cherno" channel 2. books on C++

@@tamta_asatiani oh well thx xD i was just crying xD

@@tamta_asatiani The Cherno is our idol xd

i jumped from rpgmaker 2k to gamemaker 8, and just reading the documentation for gamemaker was enough to make a lot of cool stuff, but studying computer science improved my code by a lot in gamemaker you dont need to code, you can use blocks, and then turn the blocks into code if you want to do something more complex

i am a man of many talents

I thought she was that bruce wayne from Gotham tv shows lol

if i DO add physics they'll be in the form of a proper physics object (staticbody, kinematicbody, rigidbody). if it's just gravity, it could be done to every project manually

thank you for the heads up, fixed it!

we're not fully under russia's influence. and the elections are coming up soon so things will change - for better or worse - and we'll see then

@@tamta_asatiani well i hope so, and wish you luck! and keep coding, C++ is awesome, because you can do cool things around memory layout/manipulation. (which is not possible in most higher level languages) it's so fun to know what "you have the control"

1. the debug folder includes dll files, which the exe file needs in order to run. if i didn't have the debug folder there, the user would have to manually put those into the debug folder, which i personally think it inconvenient. it's better if users can download the project file and immediately run it 2. is the circular dependency a problem? doesn't "pragma once" fix that and make sure it's included once? 3. what's the advantage of using alias = typename over macros? how do i determine which one i should use in a given situation? thank you for the advice, and also in advance for if you answer. last two are questions, i'm not arguing with you. just trying to understand the problems better

1. These files are supposed to be locally generated by your IDE/compiler/build system. The debug files are not what you're supposed to put out anyway. 2. A circular dependency is a logical error, you shouldn't self-include a header, you should use forward declarations instead. Include guards only protect against multiple inclusion of the same header. 3. That's a common practice, same as using const or constexpr instead of macros. Macros are simply pieces of code that are pasted in by the compiler at compile time, they are unintelligible to the IDE or the compiler.

​@@tamta_asatiani You can define your project's working directory so that it can(and should be) the root folder of the program. DLL files are essentially library files, and aren't necessarily debug related at all(if they WERE bult in debug, they'd be with your other DLLs and likely have a "_d" suffix or something similar). Circular dependencies will immediately cause issues in any project that actually uses the library(and even in situations where your entire ''project'' is the library you're making). If you can't get away with a forward declaration of a struct/class inside of a header, you need to rethink your design. Ideally you want to forward declare where you can anyway; you can always forward declare types in a header if the usage of a type is only a pointer/smart_ptr. typedef/using has static analysis by the compiler and will allow you to use them for things that are actually useful like creating new types, static_assertions, being able to access them as if they are a ''variable''(not exactly, but accurate enough). You basically never want to use macros for actual logic or anything that should require type checking, if you can get away with it. There are situations where macros make sense, but they are inherently dangerous, and if it's not obvious whether you should be using a macro or something, you almost certainly shouldn't be using a macro. Something that does make sense, is #ifdef and the like to control compilation flags.

​@@RexSacriticulusalso, expanding on no. 3: macros sometimes won't work with debuggers

C++ is the most popular language for game development so i don't really see a point in that first one, but i AM thinking of using windows API instead of sdl in the future

​@@tamta_asatianiwouldn't that make it Windows-only?

thank you!

Space noomad

yep

i am very much open to suggestions! like with the "sound" class and window for renderer, for example? i could pass a const ref when creating a new class, but will it hold the reference? won't the const ref then be gone bc the lifetime of the scope is over?

pfft go for it dude

@@tamta_asatiani you are awesome i hope you know that

🇧🇷