Uh oh. If you’re visiting this page, you may have found something wrong with the site.
That’s okay. Let us know and we’ll try to fix it!
- If you found something wrong with a particular tutorial of the site (e.g. a typo or incorrect example), just leave a comment on that tutorial.
- If you found something wrong with the site in general (e.g. broken functionality, the layout), please leave a comment below.
- If all else fails, use the contact form in the About/Contact section.
Thanks for helping to make the site better for everyone.
Hello Alex,
First, I want to thank you for putting this tutorial together and maintaining it! I am enjoying going this and learning.
I found a misspelled word on this page: https://www.learncpp.com/cpp-tutorial/finding-issues-before-they-become-problems/comment-page-1/#comment-399019
Section "An introduction to constraints" first word of the first sentence is missing an "s" in "Contraint-based".
Thank you again for making this available!
Mike
Thanks, the typo has been fixed.
The instructions seem to encourage the use of this form over the About/Contact form. I leave my questions here about translations, a topic I did not find addressed under "older comments".
Would you want people to translate the content here? What would be the relevant copyright concerns, if any? If people do translate your material, would you wish for the product to be somehow integrated into this site? (I assume this would be a better option for your site traffic than a simple reference to this site)
As of yet, due to the daunting amount of material to cover, I've not actual plans to do the translation. Additionally, I don't think one person can manage this alone. Assuming crowd effort at translation isn't possible on your site, perhaps one could use free mediawiki sites as an interim solution to promote hobbyists participation. In any event, I wanted to see if there are any suggestions about this. More generally, I wanted to understand the relevant preferences and policies of this site.
I've tried several methods of providing translations in the past, including having translators work on this site. In no case has the outcome been satisfactory. The amount of content is huge, and even worse, it's continually evolving, meaning translations get out of date.
At this point, I'm focused on doing an update pass on this site to incorporate new material and updated best practices, and not accepting any translation requests.
can we get this tutorial in pdf format ?
No one will forbid you to make it yourself. However, the creators of this tutorial rely on ads to finance the operation of the website and, as far as I know, will not provide a .pdf of the tutorials themselves.
Good day to you, Alex.
At first, I would like to thank you for the awesome tutorials. Now, I would like to ask (and this maybe a stupid question) what happened to the chapter names and do you plan on revising them to the pre-crash situation? For example, before the server crash there was chapter 1.4 - function return values and 1.4a - function parameters and arguments. Now, the chapter numbering has been changed and chapter order has been "messed up". I say messed up because I was following the tutorials and writing/trying the code examples based on the old numbering scheme.
The old chapter 1 was split into 3 chapters (now chapters 1-3). The content was also re-sorted into an order that I think offers a bit more of a gentle introduction to topics. Much of the existing content was extended to add additional examples, best practices, and warnings.
There is no plan to return to the prior numbering (it wouldn't make sense).
If I were you, I'd just restart from the beginning of chapter 1 -- the stuff you already know, you'll blow through quickly. But you'll inevitably encounter some new stuff of value in the topics you've already covered, and you'll also pick up the new material this way.
Makes sense. Though, now it's a PIA to rewrite everything, haha. I was trying to learn how to use cmake as well in the same process.
This is a hobby which I find rather interesting but have yet to make any significant advances.
BTW, since I mentioned it anyway - do you recommend I stick to cmake, switch to meson, or try to understand both? I'm using cmake in order to eliminate the need for an IDE (got tired of them). It was a bumpy learning experience. And I recently heard about meson while trying to fix some broken "things" with my Ubuntu.
I hate makefiles so I'm the wrong person to ask. :) Maybe Nascardriver has an opinion.
Didn't expect that, haha. If you don't mind me asking, why do you hate makefiles?
P.S.
Thank you for the assistance.
Hi Nikola!
When using CMake, one doesn't have to worry about makefiles, as they're generated automatically, Alex must have a secret other reason or he used make without CMake.
I've never used Meson, so I can't tell you which one is better. From the looks of it, it appears to be very similar to CMake. If you already know one or the other, I don't think there's a reason to switch, unless you want to know both of course.
The creators of Meson argue that CMake's language is cumbersome. I'm not a fan of CMake's language, but it's easy to use once you've got the hang of it. You're not going to spend a lot of time configuring it anyway.
Meson might be faster than CMake, I don't know that. However, as long as you're not writing a huge project, re-compilation is fast enough with CMake. You're going to need some time for a full compilation with both.
If you don't use CMake or Meson yet, go ahead and learn Meson, it sounds all right, but probably has more bugs than CMake, as it's rather new.
Well, whatever is Alex's reason for hating them, I'll stick to Cmake and makefiles :D
Gedit and its "cobalt" theme with syntax highlighting is pretty much all that I need.
Meson - maybe later, based on your explanation. Don't know if it is worth it for me considering this is just a hobby and that I'm rather bad at it altogether. I doubt I'll ever do any big project (or anything relevant) when it comes to programming, but it doesn't hurt to know.
Thank you both for your replies and keep up the good work. All the best for you.