Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
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
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
dd9e071d
Commit
dd9e071d
authored
Jan 08, 2003
by
Greg Ward
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Rewrite awkward/ungrammatical sentence.
Typo fix.
parent
5f561311
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
Doc/ext/newtypes.tex
Doc/ext/newtypes.tex
+3
-3
No files found.
Doc/ext/newtypes.tex
View file @
dd9e071d
...
@@ -52,8 +52,8 @@ typedef struct {
...
@@ -52,8 +52,8 @@ typedef struct {
}
noddy
_
NoddyObject;
}
noddy
_
NoddyObject;
\end{verbatim}
\end{verbatim}
This is what a Noddy object will contain
. In this case
nothing more
This is what a Noddy object will contain
---in this case,
nothing more
than every Python object contains
-
a refcount and a pointer to a type
than every Python object contains
, namely
a refcount and a pointer to a type
object. These are the fields the
\code
{
PyObject
_
HEAD
}
macro brings
object. These are the fields the
\code
{
PyObject
_
HEAD
}
macro brings
in. The reason for the macro is to standardize the layout and to
in. The reason for the macro is to standardize the layout and to
enable special debugging fields in debug builds. Note that there is
enable special debugging fields in debug builds. Note that there is
...
@@ -61,7 +61,7 @@ no semicolon after the \code{PyObject_HEAD} macro; one is included in
...
@@ -61,7 +61,7 @@ no semicolon after the \code{PyObject_HEAD} macro; one is included in
the macro definition. Be wary of adding one by accident; it's easy to
the macro definition. Be wary of adding one by accident; it's easy to
do from habit, and your compiler might not complain, but someone
do from habit, and your compiler might not complain, but someone
else's probably will! (On Windows, MSVC is known to call this an
else's probably will! (On Windows, MSVC is known to call this an
error and refuse to
produce compiled
code.)
error and refuse to
compile the
code.)
For contrast, let's take a look at the corresponding definition for
For contrast, let's take a look at the corresponding definition for
standard Python integers:
standard Python integers:
...
...
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