From 176fcde72663e4cee4f09eb77acbc55e5add1104 Mon Sep 17 00:00:00 2001 From: Manuel Date: Tue, 10 Jun 2025 19:42:35 +0200 Subject: [PATCH] Updated Using raylib with Cpp (markdown) --- Using-raylib-with-Cpp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-raylib-with-Cpp.md b/Using-raylib-with-Cpp.md index 0a5aeb7..a79f4f4 100644 --- a/Using-raylib-with-Cpp.md +++ b/Using-raylib-with-Cpp.md @@ -30,7 +30,7 @@ DrawText(my_string.c_str(),0,0,20,RED); It is a common Object Oriented pattern to use Resource Acquisition Is Initialization (RAII). It may seem obvious to use this pattern with textures and models in raylib. This is possible to do, but the developer must be aware of the object lifetime, and when copies are made. For shared resources you need to follow the rule of 5 (https://en.cppreference.com/w/cpp/language/rule_of_three). It is very common for new developer to make a class like this to automatically load an unload textures when things are created or go out of scope. -``` +```cpp class MySprite { private: