Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Gwenaël Samain
cython
Commits
cc3b4267
Commit
cc3b4267
authored
May 04, 2008
by
Gabriel Gellner
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added struct table. Needed to avoid using spanned cells as it breaks the latex output.
parent
eb39c410
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
12 deletions
+32
-12
docs/external_C_code.rst
docs/external_C_code.rst
+32
-12
No files found.
docs/external_C_code.rst
View file @
cc3b4267
...
@@ -159,18 +159,38 @@ header file, and the corresponding Cython declaration that you should put in
...
@@ -159,18 +159,38 @@ header file, and the corresponding Cython declaration that you should put in
the ``cdef extern`` from block. Struct declarations are used as an example; the
the ``cdef extern`` from block. Struct declarations are used as an example; the
same applies equally to union and enum declarations.
same applies equally to union and enum declarations.
.. TODO: put table here...
+-------------------------+---------------------------------------------+-----------------------------------------------------------------------+
| C code | Possibilities for corresponding Cython Code | Comments |
+-----------------+--------------------+
+=========================+=============================================+=======================================================================+
| C code | Cython |
| :: | :: | Cython will refer to the as ``struct Foo`` in the generated C code. |
+-----------------+--------------------+
| | | |
| :: | :: |
| struct Foo { | cdef struct Foo: | |
| | |
| ... | ... | |
| struct Foo { | cdef struct Foo: |
| }; | | |
| ... | ... |
+-------------------------+---------------------------------------------+-----------------------------------------------------------------------+
| }; | |
| :: | :: | Cython will refer to the type simply as ``Foo`` in |
+-----------------+--------------------+
| | | the generated C code. |
| typedef struct { | ctypedef struct Foo: | |
| ... | ... | |
| } Foo; | | |
+-------------------------+---------------------------------------------+-----------------------------------------------------------------------+
| :: | :: | If the C header uses both a tag and a typedef with *different* |
| | | names, you can use either form of declaration in Cython |
| typedef struct foo { | cdef struct foo: | (although if you need to forward reference the type, |
| ... | ... | you'll have to use the first form). |
| } Foo; | ctypedef foo Foo #optional | |
| | | |
| | or:: | |
| | | |
| | ctypedef struct Foo: | |
| | ... | |
+-------------------------+---------------------------------------------+-----------------------------------------------------------------------+
| :: | :: | If the header uses the *same* name for the tag and typedef, you |
| | | won't be able to include a :keyword:`ctypedef` for it -- but then, |
| typedef struct Foo { | cdef struct Foo: | it's not necessary. |
| ... | ... | |
| } Foo; | | |
+-------------------------+---------------------------------------------+-----------------------------------------------------------------------+
Note that in all the cases below, you refer to the type in Cython code simply
Note that in all the cases below, you refer to the type in Cython code simply
as :ctype:`Foo`, not ``struct Foo``.
as :ctype:`Foo`, not ``struct Foo``.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment