From c25967a0942526b04a6be8041f2db659b197b581 Mon Sep 17 00:00:00 2001 From: Rene Rivera Date: Sun, 27 Feb 2005 17:28:24 +0000 Subject: [PATCH] Apply typo fixes from Julio M. Merino Vidal [SVN r27513] --- doc/PyConDC_2003/bpl_mods.txt | 6 +++--- doc/new-conversions.html | 2 +- doc/v2/errors.html | 2 +- doc/v2/type_id.html | 2 +- include/boost/python/converter/registry.hpp | 2 +- include/boost/python/object/iterator.hpp | 2 +- src/object/inheritance.cpp | 4 ++-- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/PyConDC_2003/bpl_mods.txt b/doc/PyConDC_2003/bpl_mods.txt index e243cda9..5800f00b 100644 --- a/doc/PyConDC_2003/bpl_mods.txt +++ b/doc/PyConDC_2003/bpl_mods.txt @@ -273,7 +273,7 @@ correctly: ================== This section outlines some of the library's major features. Except as -neccessary to avoid confusion, details of library implementation are +necessary to avoid confusion, details of library implementation are omitted. ------------------------------------------- @@ -537,7 +537,7 @@ This has two effects: called with an object wrapping a ``Derived`` instance. Wrapped member functions of class ``T`` are treated as though they have an implicit first argument of ``T&``, so these conversions are - neccessary to allow the base class methods to be called for derived + necessary to allow the base class methods to be called for derived objects. Of course it's possible to derive new Python classes from wrapped C++ @@ -650,7 +650,7 @@ Things to notice about the dispatcher class: called on an object of type ``BaseWrap``, since it overrides ``f``. Admittedly, this formula is tedious to repeat, especially on a project -with many polymorphic classes; that it is neccessary reflects +with many polymorphic classes; that it is necessary reflects limitations in C++'s compile-time reflection capabilities. Several efforts are underway to write front-ends for Boost.Python which can generate these dispatchers (and other wrapping code) automatically. diff --git a/doc/new-conversions.html b/doc/new-conversions.html index 9aec43cd..e953ce0e 100644 --- a/doc/new-conversions.html +++ b/doc/new-conversions.html @@ -260,7 +260,7 @@ a request which helps to eliminate redundancy. The rules used to
  1. Treat built-in types specially: when unwrapping a value or constant reference to one of these, use a value for the target - type. It will bind to a const reference if neccessary, and more + type. It will bind to a const reference if necessary, and more importantly, avoids having to dynamically allocate room for an lvalue of types which can be cheaply copied.
  2. diff --git a/doc/v2/errors.html b/doc/v2/errors.html index a8a77da1..75d53c95 100644 --- a/doc/v2/errors.html +++ b/doc/v2/errors.html @@ -126,7 +126,7 @@ void handle_exception() throw();
    Rationale: At inter-language boundaries it is important to ensure that no C++ exceptions escape, since the calling language - usually doesn't have the equipment neccessary to properly unwind the + usually doesn't have the equipment necessary to properly unwind the stack. Use handle_exception to manage exception translation whenever your C++ code is called directly from the Python API. This is done for you automatically by the usual function wrapping diff --git a/doc/v2/type_id.html b/doc/v2/type_id.html index bb906154..59025e0f 100755 --- a/doc/v2/type_id.html +++ b/doc/v2/type_id.html @@ -121,7 +121,7 @@ type_info(std::type_info const& = typeid(void));
    Effects: constructs a type_info object which identifies the same type as its argument.
    -
    Rationale: Since it is occasionally neccessary to make an +
    Rationale: Since it is occasionally necessary to make an array of type_info objects a benign default argument is supplied. Note: this constructor does not correct for non-conformance of compiler diff --git a/include/boost/python/converter/registry.hpp b/include/boost/python/converter/registry.hpp index 8e7497d9..131cca72 100644 --- a/include/boost/python/converter/registry.hpp +++ b/include/boost/python/converter/registry.hpp @@ -17,7 +17,7 @@ struct registration; // This namespace acts as a sort of singleton namespace registry { - // Get the registration corresponding to the type, creating it if neccessary + // Get the registration corresponding to the type, creating it if necessary BOOST_PYTHON_DECL registration const& lookup(type_info); // Return a pointer to the corresponding registration, if one exists diff --git a/include/boost/python/object/iterator.hpp b/include/boost/python/object/iterator.hpp index e8a4da00..7b9810ec 100644 --- a/include/boost/python/object/iterator.hpp +++ b/include/boost/python/object/iterator.hpp @@ -109,7 +109,7 @@ struct iterator_range namespace detail { // Get a Python class which contains the given iterator and - // policies, creating it if neccessary. Requires: NextPolicies is + // policies, creating it if necessary. Requires: NextPolicies is // default-constructible. template object demand_iterator_class(char const* name, Iterator* = 0, NextPolicies const& policies = NextPolicies()) diff --git a/src/object/inheritance.cpp b/src/object/inheritance.cpp index 7ae3642d..7d542865 100644 --- a/src/object/inheritance.cpp +++ b/src/object/inheritance.cpp @@ -203,7 +203,7 @@ namespace return &*p; } - // Get the entry for a type, inserting if neccessary + // Get the entry for a type, inserting if necessary inline type_index_t::iterator demand_type(class_id type) { type_index_t::iterator p = type_position(type); @@ -218,7 +218,7 @@ namespace return type_index().insert(p, boost::make_tuple(type, v, dynamic_id_function(0))); } - // Map a two types to a vertex in the graph, inserting if neccessary + // Map a two types to a vertex in the graph, inserting if necessary typedef std::pair type_index_iterator_pair;