From cdf68e807158c29905359a2cc2c2a0cfcd20c142 Mon Sep 17 00:00:00 2001
From: Sebastien Gilles <sebastien.gilles@inria.fr>
Date: Mon, 3 Oct 2022 14:00:18 +0200
Subject: [PATCH] Revert misguided correction.
---
5-UsefulConceptsAndSTL/1-ErrorHandling.ipynb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/5-UsefulConceptsAndSTL/1-ErrorHandling.ipynb b/5-UsefulConceptsAndSTL/1-ErrorHandling.ipynb
index 076b4c7..a3600d3 100644
--- a/5-UsefulConceptsAndSTL/1-ErrorHandling.ipynb
+++ b/5-UsefulConceptsAndSTL/1-ErrorHandling.ipynb
@@ -494,7 +494,7 @@
"I don't like these error codes much, because:\n",
"\n",
"* The result can't be naturally given in return value and must be provided in argument.\n",
- "* You have to bookkeep the possible error codes somewhere, and an user must know this somewhere to go consult them if something happens (usually a header file: see for instance one for [PETSc library](https://www.mcs.anl.gov/petsc/petsc-master/include/petscerror.h.html)).\n",
+ "* You have to bookkeep the possible error codes somewhere, and a user must know this somewhere to go consult them if something happens (usually a header file: see for instance one for [PETSc library](https://www.mcs.anl.gov/petsc/petsc-master/include/petscerror.h.html)).\n",
"* In the libraries that use them, more often than not some are not self descriptive and you have to figure out what the hell the issue is.\n",
"* And more importantly, this relies on the end-user thinking to check the error value:"
]
--
GitLab