From a30ffa3736397c285fce6aee8035755f154d8928 Mon Sep 17 00:00:00 2001 From: Brett Date: Fri, 14 Mar 2025 00:57:35 -0400 Subject: [PATCH] night --- CMakeLists.txt | 2 +- src/michael_examples.cpp | 31 +++++++++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index a57387a..75bbce0 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -51,7 +51,7 @@ macro(blt_add_project name source type) project(tower-defense) endmacro() -project(tower-defense VERSION 0.0.6) +project(tower-defense VERSION 0.0.7) option(ENABLE_ADDRSAN "Enable the address sanitizer" OFF) option(ENABLE_UBSAN "Enable the ub sanitizer" OFF) diff --git a/src/michael_examples.cpp b/src/michael_examples.cpp index 1aaf38b..9b6e74d 100644 --- a/src/michael_examples.cpp +++ b/src/michael_examples.cpp @@ -44,6 +44,8 @@ // class member (private) variables should be prefixed with m_ // prefer enum class defs over enum defs, they are namespaced. +void refs(); + void michael_examples() { /* @@ -236,5 +238,34 @@ void michael_examples() // this is called a structured binding. You can use it to unpack structs. enumerate returns a tuple of for (const auto [i, v] : blt::enumerate(vector_of_rules)) v = rule_of_5_t{static_cast(i)}; + + // Oh, right the fun of C++'s casting. + // In C and Java you have the C-style cast (Type) variable. + // This is not good practice in C++ + // In C++ we have: (C-style casts will do one of these in some order based on what the compiler thinks is best. Not a good idea) + // this one is the one you basically always want: + // static_cast(expression) -> converts the expression to the type. works for static type conversions, eg: int to float + // dynamic_cast(expression) -> is used for OOP stuff. Is used to convert base class to derived class (I avoid OOP) + // -- Danger Land - + // reinterpret_cast(&expression) -> tells the compiler we would like to interpret the pointer as this type. + // This type of cast can be very dangerous, it is undefined behaviour in a lot of cases if you are not careful. + // I do not remember all the silly rules with it. Basically: it works how you think it does until it doesn't + // const_cast(expression) -> can be used to add or remove const from an expression + // this can also create terrible UB. (imagine you make something const, then cast away that const and modify the underlying variable. + // That is major UB and will cause major problems at some point. } + + BLT_TRACE(""); + BLT_TRACE(""); + + // Ok I think that covers the basics of copy and move semantics, lets quickly touch on blt::iterators + + + // show off reference stuff + refs(); } + +void refs() +{ + +} \ No newline at end of file