From df200ba3c1c32592802bcefe366ab47677890d5d Mon Sep 17 00:00:00 2001 From: Jeffery Myers Date: Sun, 12 May 2024 10:18:45 -0700 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 da283f9..684eccb 100644 --- a/Using-raylib-with-Cpp.md +++ b/Using-raylib-with-Cpp.md @@ -27,7 +27,7 @@ DrawText(my_string.c_str(),0,0,20,RED); ``` # Shared GPU resources in constructors and destructors. -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 ware 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 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. ```