Fix typos in src/Base
This commit is contained in:
@@ -53,9 +53,9 @@ using namespace Base;
|
||||
|
||||
PyException::PyException(const Py::Object &obj) {
|
||||
_sErrMsg = obj.as_string();
|
||||
// WARNING: we are assumming that python type object will never be
|
||||
// destroied, so we don't keep reference here to save book-keeping in
|
||||
// our copy constructor and desctructor
|
||||
// WARNING: we are assuming that python type object will never be
|
||||
// destroyed, so we don't keep reference here to save book-keeping in
|
||||
// our copy constructor and destructor
|
||||
_exceptionType = (PyObject*)obj.ptr()->ob_type;
|
||||
_errorType = obj.ptr()->ob_type->tp_name;
|
||||
}
|
||||
@@ -84,9 +84,9 @@ PyException::PyException(void)
|
||||
_exceptionType = PP_last_exception_type;
|
||||
|
||||
if(PP_last_exception_type) {
|
||||
// WARNING: we are assumming that python type object will never be
|
||||
// destroied, so we don't keep reference here to save book-keeping in
|
||||
// our copy constructor and desctructor
|
||||
// WARNING: we are assuming that python type object will never be
|
||||
// destroyed, so we don't keep reference here to save book-keeping in
|
||||
// our copy constructor and destructor
|
||||
Py_DECREF(PP_last_exception_type);
|
||||
PP_last_exception_type = 0;
|
||||
|
||||
|
||||
@@ -951,7 +951,7 @@ Matrix4D& Matrix4D::Hat(const Vector3d& rV)
|
||||
int Matrix4D::hasScale(double tol) const {
|
||||
// check for uniform scaling
|
||||
//
|
||||
// scaling factors are the colum vector length. We use square distance and
|
||||
// scaling factors are the column vector length. We use square distance and
|
||||
// ignore the actual scaling signess
|
||||
//
|
||||
if(!tol)
|
||||
|
||||
@@ -201,7 +201,7 @@ PP_Run_Known_Callable(PyObject *object, /* func|class|method */
|
||||
* so you should call one of these, one time, per exception:
|
||||
* caveats: not thread-specific since saves data in globals,
|
||||
* and only exports traceback object (the exception type and
|
||||
* data are converted to text strings and disgarded); the
|
||||
* data are converted to text strings and discarded); the
|
||||
* PyErr_Print() built-in also does a bit more on syntax errors,
|
||||
* and sends its text to sys.stderr: in principle, we could
|
||||
* assign stderr to a StringIO object and call PyErr_Print, but
|
||||
|
||||
Reference in New Issue
Block a user