It’s been an incredibly productive week for me in terms of soaking myself in C++ dark holy waters. I gave up on the idea of having “well-written” C++ in the sense that I don’t think I can get this right this year. I need to read a LOT of code before I can get the gist of writing C++ in an acceptable manner.

By what measure would it be acceptable? Obviously not by internet “standards”, at the very least I want to feel peace of mind that I’m not creating a tiny little black holes every time I compile an application.

An example of what I mean: (explanation taken from

What’s the difference between “const X* p”, “X* const p” and “const X* const p”?

Read the pointer declarations right-to-left.

const X* p means “p points to an X that is const”: the X object can’t be changed via p.

X* const p means “p is a const pointer to an X that is non-const”: you can’t change the pointer p itself, but you can change the X object via p.

const X* const p means “p is a const pointer to an X that is const”: you can’t change the pointer p itself, nor can you change the X object via p.

At my stage, I shouldn’t worry about things like these right now as I’m not building a library or complex code that requires that. However, I can’t really turn an eye on it and pretend it doesn’t exist either.

Thus, for me this issue would be best to attend to as it happen.

In the meantime, I’ve been working my brains off studying Qt Framework which I believe will really help me in the future. I finally feel comfortable working with it even though what I write in C++ feels incredibly messy.

That said, I’m looking forward to new challenges.

Before you comment

  • You can use Markdown in your comments, here's a guide.
  • Keep things civil.
  • That means don't do personal attacks.
  • Profanity is highly discouraged.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.