diff --git a/7-Appendix/CompilationErrors.ipynb b/7-Appendix/CompilationErrors.ipynb index ab768ba8c64576c464dd388de035328e90b7432c..bc6b28dcb10b3f4c6034cc1bf3ef82d157c3bd54 100644 --- a/7-Appendix/CompilationErrors.ipynb +++ b/7-Appendix/CompilationErrors.ipynb @@ -43,7 +43,7 @@ "\n", "This is especially true after very usual mistakes such as missing ')', '}' or ';'.\n", "\n", - "So what I (Sébastien) do is almost always begin at the top of the errors and see if solving this one explain the following errors or not.\n", + "So what I (Sébastien) do is almost always begin at the top of the errors and see if solving this one explains the following errors or not.\n", "\n", "I sometimes even redirect the output of the compilation into a file so that I can easily access the top. To my knowledge there's no clean way to do it more properly with the build tool directly; I would be delighted if someone proved me wrong on this one because the following sequence is not entirely satisfactory:\n" ] @@ -97,7 +97,7 @@ "id": "9", "metadata": {}, "source": [ - "It's especially useful when you modified an header file that is heavily used directly or indirectly in your program or your library - all files that depend on it will in this case be recompiled.\n", + "It's especially useful when you modified a header file that is heavily used directly or indirectly in your program or your library - all files that depend on it will in this case be recompiled.\n", "\n", "But why talk about it here, in a notebook about compilation errors?\n", "\n", @@ -165,9 +165,9 @@ "source": [ "## Read carefully the message\n", "\n", - "As said in the introduction, compilers are now much more helpful now that what they used to be (see for instance in the example above: it even tries to tell me where exactly in the line the error occurs).\n", + "As said in the introduction, compilers are now much more helpful now than what they used to be (see for instance in the example above: it even tries to tell me where exactly in the line the error occurs).\n", "\n", - "Most of the error messages are now clear enough; when they're not you may find information on the Web as the question has surely be posted somewhere (StackOverflow or similar sites).\n", + "Most of the error messages are now clear enough; when they're not you may find information on the Web as the question has surely been posted somewhere (StackOverflow or similar sites).\n", "\n", "c++filt (that we mentioned [here](../6-InRealEnvironment/3-Compilers.ipynb#c++filt)) may be of help if the mangling makes the name of your function / class / whatever too difficult to read." ] @@ -250,9 +250,9 @@ "\n", "In both the cases we covered in this notebook, we rejoiced that the compiler was rather helpful if you forgot to use properly one of the expected keyword... but for the `template` keyword (described [here](../4-Templates/3-Syntax.ipynb#Mandatory-template-keyword)) it is fairly recent (around 2022!) - so if you're using a not so recent compiler and get an error message about an unknown method whereas \n", "\n", - "- This method do exist\n", - "- This method is properly declared at to calling site (it's not a missing include)\n", - "- This method is a template method within a template class\n", + "- The method does exist\n", + "- The method is properly declared at to calling site (it's not a missing include)\n", + "- The method is a template method within a template class\n", "\n", "then you should have a look at the explanation in the notebook about the `template` keyword.\n", "\n"