home.social

Search

1000 results for “cpp”

  1. So, the next one thing! "Dima stand 🧍‍♂️" (codeberg.org/xolatgames/Dima-s) now uses Assimp as a library for parsing 3D model files (instead of the parser that I was wrote by my own), and even Bullet Physics SDK for creation some 3D physic.

    #cpp #cplusplus #cmake #assimp #bullet3 #bullet #3d #3dgame #simulator #codeberg #opensource #codelite #linux #stb #stb_image #blender #blender3d #gimp #gimp3 #glfw #glfw3 #opengl #glm

  2. So, the next one thing! "Dima stand 🧍‍♂️" (codeberg.org/xolatgames/Dima-s) now uses Assimp as a library for parsing 3D model files (instead of the parser that I was wrote by my own), and even Bullet Physics SDK for creation some 3D physic.

    #cpp #cplusplus #cmake #assimp #bullet3 #bullet #3d #3dgame #simulator #codeberg #opensource #codelite #linux #stb #stb_image #blender #blender3d #gimp #gimp3 #glfw #glfw3 #opengl #glm

  3. Day 10/75: Sliding window - variable size

    Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.

    The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.

    #CPP #DSA #Algorithms

  4. Day 10/75: Sliding window - variable size

    Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.

    The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.

    #CPP #DSA #Algorithms

  5. Day 10/75: Sliding window - variable size

    Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.

    The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.

    #CPP #DSA #Algorithms

  6. Day 10/75: Sliding window - variable size

    Today's note was about using a stable invariant so sliding window - variable size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.

    The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.

    #CPP #DSA #Algorithms

  7. Today is the 8th anniversary of C++ Insights. In my latest post, I discuss its status and the gift for this special day.

    andreasfertig.com/blog/2026/05

    #cpp26 #cppinsights

  8. Today is the 8th anniversary of C++ Insights. In my latest post, I discuss its status and the gift for this special day.

    andreasfertig.com/blog/2026/05

    #cpp26 #cppinsights

  9. Today is the 8th anniversary of C++ Insights. In my latest post, I discuss its status and the gift for this special day.

    andreasfertig.com/blog/2026/05

    #cpp26 #cppinsights

  10. Today is the 8th anniversary of C++ Insights. In my latest post, I discuss its status and the gift for this special day.

    andreasfertig.com/blog/2026/05

  11. Today is the 8th anniversary of C++ Insights. In my latest post, I discuss its status and the gift for this special day.

    andreasfertig.com/blog/2026/05

    #cpp26 #cppinsights