Commit d3d729e3 authored by Robert Bradshaw's avatar Robert Bradshaw

Merge pull request #467 from jwilk/spelling

docs: Fix typos.
parents adf3c18b 00141382
...@@ -415,7 +415,7 @@ Configurable optimisations ...@@ -415,7 +415,7 @@ Configurable optimisations
``optimize.unpack_method_calls`` (True / False) ``optimize.unpack_method_calls`` (True / False)
Cython can generate code that optimistically checks for Python method objects Cython can generate code that optimistically checks for Python method objects
at call time and unpacks the underlying function to call it directly. This at call time and unpacks the underlying function to call it directly. This
can substantially speed up method calls, especially for bultins, but may also can substantially speed up method calls, especially for builtins, but may also
have a slight negative performance impact in some cases where the guess goes have a slight negative performance impact in some cases where the guess goes
completely wrong. completely wrong.
Disabling this option can also reduce the code size. Default is True. Disabling this option can also reduce the code size. Default is True.
......
...@@ -314,11 +314,11 @@ Subclassing ...@@ -314,11 +314,11 @@ Subclassing
* If the base type is a built-in type, it must have been previously declared as an ``extern`` extension type. * If the base type is a built-in type, it must have been previously declared as an ``extern`` extension type.
* ``cimport`` can be used to import the base type, if the extern declared base type is in a ``.pxd`` definition file. * ``cimport`` can be used to import the base type, if the extern declared base type is in a ``.pxd`` definition file.
* In Cython, multiple inheritance is not permitted.. singlular inheritance only * In Cython, multiple inheritance is not permitted.. singular inheritance only
* Cython extenstion types can also be sub-classed in Python. * Cython extension types can also be sub-classed in Python.
* Here multiple inhertance is permissible as is normal for Python. * Here multiple inheritance is permissible as is normal for Python.
* Even multiple extension types may be inherited, but C-layout of all the base classes must be compatible. * Even multiple extension types may be inherited, but C-layout of all the base classes must be compatible.
...@@ -448,7 +448,7 @@ External ...@@ -448,7 +448,7 @@ External
print "Imag:", c.cval.imag print "Imag:", c.cval.imag
.. note:: Some important things in the example: .. note:: Some important things in the example:
#. ``ctypedef`` has been used because Python's header file has the struct decalared with:: #. ``ctypedef`` has been used because Python's header file has the struct declared with::
ctypedef struct { ctypedef struct {
... ...
......
...@@ -164,7 +164,7 @@ write a short script to profile our code:: ...@@ -164,7 +164,7 @@ write a short script to profile our code::
Running this on my box gives the following output:: Running this on my box gives the following output::
TODO: how to display this not as code but verbatimly? TODO: how to display this not as code but verbatim?
Sat Nov 7 17:40:54 2009 Profile.prof Sat Nov 7 17:40:54 2009 Profile.prof
......
...@@ -649,7 +649,7 @@ When you declare:: ...@@ -649,7 +649,7 @@ When you declare::
the name Spam serves both these roles. There may be other names by which you the name Spam serves both these roles. There may be other names by which you
can refer to the constructor, but only Spam can be used as a type name. For can refer to the constructor, but only Spam can be used as a type name. For
example, if you were to explicity import MyModule, you could use example, if you were to explicitly import MyModule, you could use
``MyModule.Spam()`` to create a Spam instance, but you wouldn't be able to use ``MyModule.Spam()`` to create a Spam instance, but you wouldn't be able to use
:class:`MyModule.Spam` as a type name. :class:`MyModule.Spam` as a type name.
......
...@@ -94,7 +94,7 @@ It currently supports OpenMP, but later on more backends might be supported. ...@@ -94,7 +94,7 @@ It currently supports OpenMP, but later on more backends might be supported.
The ``chunksize`` argument indicates the chunksize to be used for dividing the iterations among threads. The ``chunksize`` argument indicates the chunksize to be used for dividing the iterations among threads.
This is only valid for ``static``, ``dynamic`` and ``guided`` scheduling, and is optional. Different chunksizes This is only valid for ``static``, ``dynamic`` and ``guided`` scheduling, and is optional. Different chunksizes
may give substatially different performance results, depending on the schedule, the load balance it provides, may give substantially different performance results, depending on the schedule, the load balance it provides,
the scheduling overhead and the amount of false sharing (if any). the scheduling overhead and the amount of false sharing (if any).
Example with a reduction:: Example with a reduction::
......
...@@ -166,7 +166,7 @@ version 0.17, Cython also allows to pass external source files into the ...@@ -166,7 +166,7 @@ version 0.17, Cython also allows to pass external source files into the
And in the .pyx source file, write this into the first comment block, before And in the .pyx source file, write this into the first comment block, before
any source code, to compile it in C++ mode and link it statically against the any source code, to compile it in C++ mode and link it statically against the
:file:`Rectange.cpp` code file:: :file:`Rectangle.cpp` code file::
# distutils: language = c++ # distutils: language = c++
# distutils: sources = Rectangle.cpp # distutils: sources = Rectangle.cpp
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment