C++ - Reddit
227 subscribers
48 photos
8 videos
1 file
25.4K links
Stay up-to-date with everything C++!
Content directly fetched from the subreddit just for you.

Join our group for discussions : @programminginc

Powered by : @r_channels
Download Telegram
New Videos On The CppCon YouTube Channel - 03/25/23 - 03/31/23

This week the CppCon YouTube channel released the following videos

* Lightning Talk: find-move-candidates in Cpp - Chris Cotter - [https://youtu.be/F8wbpi2kTmY](https://youtu.be/F8wbpi2kTmY)
* Lightning Talk: C++20 - A New Way of Meta-Programming? - Kris Jusiak - [https://youtu.be/zRYlQGMdISI](https://youtu.be/zRYlQGMdISI)
* Lightning Talk: Adventures in Benchmarking Timestamp Taking in Cpp - Nataly Rasovsky - [https://youtu.be/-XU2silGr6g](https://youtu.be/-XU2silGr6g)
* Lightning Talk: 10 Things an Entry-Level Software Engineer Asks You to Do - Katherine Rocha - [https://youtu.be/RkH8P1RgYIs](https://youtu.be/RkH8P1RgYIs)
* Lightning Talk: majsdown: Metaprogramming? In my Slides? - Vittorio Romeo - [https://youtu.be/vbhaZHpomg0](https://youtu.be/vbhaZHpomg0)
* Lightning Talk: Const Mayhem in C++ - Ofek Shilon - [https://youtu.be/cuQKiXZUmyA](https://youtu.be/cuQKiXZUmyA)
* Lightning Talk: Now in Our Lifetimes Cpp - Staffan Tjernstrom - [https://youtu.be/pLVg3c6bljE](https://youtu.be/pLVg3c6bljE)

https://redd.it/127hb5r
@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
Understanding C++ File Extensions and the GCC Compilation Process

**Different C++ File Extensions**: In C++, you can use various file extensions like .cc, .cp, .cxx, .cpp, .c++, and .c. 

 **GCC: The Versatile Compiler**: GCC can handle all these extensions easily. 

 **Converting .cpp Files**:

* **Preprocessing**: Turn .cpp files into .ii files to get better debugging information.
* **Assembly**: Change .cpp files into .s files to see the low-level code.
* **Object Code**: Compile .cpp files into .o files to prepare for making an executable. 

 **Important GCC Options**:

* **-E**: Preprocess only.
* **-S**: Compile to assembly code.
* **-c**: Compile to object code.

For example: 

// Compile the code to executable:
g++ prog1.cpp -o prog1

// Generate preprocessed CPP program:
g++ -E prog1.cpp -o prog1.ii

// Generate assembly code:
g++ -S prog1.cpp -o prog1.s

// Compile preprocessed code to object file:
g++ -c prog1.ii -o prog1.o

// Alternatively, compile directly from source to object file:
g++ -c prog1.cpp -o prog1.o

 **Building a Command**:

g++ [options] [source files] [object files] [libraries] -o output_file

 **Why Learn This?** Knowing these details makes you more efficient in developing and debugging C++ programs. It’s especially useful for senior software engineers who want to write better, optimized code.

 #SoftwareEngineering #CPP #GCC #Programming #CodeOptimization #Debugging #CompilerOptions #CodingTips



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