Opengl tutorial series | #6 | Pass data between shaders and C file
https://youtube.com/watch?v=NmJ2BlLebdA&feature=share

https://redd.it/12svira
@r_cpp

I've been working on a little AI assistant in C++ I named NullusAI for a university project. You can check the progress of this little project on my Twitter.
https://twitter.com/Jorge_G_P_/status/1640076035831070723

https://redd.it/1370y3z
@r_cpp

How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)

Hey guys! My name is Tarik Brown and I am a software engineer at Microsoft who works on the C/C++ Extension for VS Code. I’ve decided to start a tutorial series starting with how to setup VS Code for C/C++ Development. Check out the video here: https://youtu.be/bCK36Tesrvc

https://redd.it/13tzgjl
@r_cpp

CppCon 2022 Lightning Talk: Cpp Change Detector Tests
https://www.youtube.com/watch?v=rv-zHn_Afko

https://redd.it/14d6dg4
@r_cpp

[C++20] [[no_unique_address]] for 1 byte message views
https://twitter.com/krisjusiak/status/1674351951138414592

https://redd.it/14m0lf7
@r_cpp

Published a new video on stdin, stdout and stderr, You are welcomed to have a look

https://youtu.be/p13AiUvK6fY?feature=shared

https://redd.it/16l6aeh
@r_cpp

Order of executing function calls by compiler

\#cpp \#compilers \#code\_execution Interesting case in testing quiz: Any ideas which method from foo1 and foo2 will be executed first?

int foo1() {}
int foo2() {}

void bar(int a, int b) {}

int main() {
bar(foo1(), foo2());
}

​

​

https://redd.it/17dzglp
@r_cpp

Test language speed the best way
https://youtu.be/pwTSv-4Cp40

https://redd.it/17j00yq
@r_cpp

Abusing the C++ preprocessor for declaring Rust-like traits
https://twitter.com/maximmkaaa/status/1722050919540343019

https://redd.it/17q9dg4
@r_cpp

boost::interprocessexception::libraryerror

Hi , Im using a boost version of 1.61 for shared memory mangement.
The issue is that the application crashes as a result of "Error 18" in boost library a.k.a size_error.
\#OS - windows 10 version - 22H2 build 19045.3693.
\#CPP - 14,
\#boostVer - 1.61


try {


boost::interprocess::sharedmemoryobject::remove(msSharedMemoryName.cstr());
bipc::managedsharedmemory seg(bipc::openorcreate, msSharedMemoryName.cstr(), mnSharedMemoryMaxSize, ptr, perm);



}
catch (const boost::interprocess::interprocessexception& ex) {
std::cerr << "Error: " << ex.what()<<" error code"<< ex.geterrorcode() << std::endl;
return 1;
}

When constructing seg the error reproduces

&#x200B;

The issue only occurs on a specific computer , on other computers with the same OS and build version the problem does not occur.

https://redd.it/17zmkaz
@r_cpp

Create towers of hanoi simulation in C++
https://www.youtube.com/watch?v=u1QP9WiOWWM

https://redd.it/183eq7w
@r_cpp

The Hunt for the Elusive Bug: A C++ Developer's Odyssey



Hey C++ aficionados of r/cpp,

Prepare yourselves for a saga from the trenches of C++ development—a tale of perseverance, frustration, and the relentless pursuit of elusive bugs. Join me on a journey through the labyrinthine corridors of code, where attention to detail reigns supreme and every misplaced semicolon is a potential landmine.

Imagine yourself knee-deep in C++ code, navigating the treacherous waters of memory management and pointer arithmetic. You're on the trail of a bug that has eluded capture for far too long—a bug that mocks your efforts with its stubborn resilience.

Hours turn into days as you comb through your codebase, searching for the elusive culprit that dares to defy your logic. And then, just when you're on the brink of despair, you spot it—a tiny oversight that has evaded your gaze until now: a missing long keyword. Such a seemingly innocuous detail, yet its absence has thrown your entire project into disarray, leaving you grappling with frustration and disbelief.

But in the world of C++, where elegance meets complexity, every bug is a lesson waiting to be learned. You debug, you iterate, and you emerge stronger than before, armed with newfound knowledge and a steely resolve.

So, to all my fellow C++ developers, I offer this advice: Embrace the challenge of debugging, for it is through the crucible of trial and error that we refine our craft. Stay vigilant, stay determined, and never underestimate the importance of attention to detail in the pursuit of elegant solutions.

Have you ever encountered a bug that tested your patience in the world of C++? Share your tales of triumph (or tribulation) in the comments below!

Link to "Powers of Ten" Video

Comments are welcome!

https://redd.it/1c99bxa
@r_cpp