Skip to content
Projeler
Gruplar
Parçacıklar
Yardım
Yükleniyor...
Oturum aç / Kaydol
Gezinmeyi değiştir
C
cpython
Proje
Proje
Ayrıntılar
Etkinlik
Cycle Analytics
Depo (repository)
Depo (repository)
Dosyalar
Kayıtlar (commit)
Dallar (branch)
Etiketler
Katkıda bulunanlar
Grafik
Karşılaştır
Grafikler
Konular (issue)
0
Konular (issue)
0
Liste
Pano
Etiketler
Kilometre Taşları
Birleştirme (merge) Talepleri
0
Birleştirme (merge) Talepleri
0
CI / CD
CI / CD
İş akışları (pipeline)
İşler
Zamanlamalar
Grafikler
Paketler
Paketler
Wiki
Wiki
Parçacıklar
Parçacıklar
Üyeler
Üyeler
Collapse sidebar
Close sidebar
Etkinlik
Grafik
Grafikler
Yeni bir konu (issue) oluştur
İşler
Kayıtlar (commit)
Konu (issue) Panoları
Kenar çubuğunu aç
Batuhan Osman TASKAYA
cpython
Commits
43af5b58
Kaydet (Commit)
43af5b58
authored
Agu 06, 2002
tarafından
Guido van Rossum
Dosyalara gözat
Seçenekler
Dosyalara Gözat
İndir
Eposta Yamaları
Sade Fark
Add some fine points: METH_KEYWORDS implies METH_VARARGS, and ob_size
is no longer unused in type objects.
üst
8ee52434
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
6 deletions
+10
-6
newtypes.tex
Doc/api/newtypes.tex
+10
-6
No files found.
Doc/api/newtypes.tex
Dosyayı görüntüle @
43af5b58
...
@@ -221,7 +221,9 @@ The \member{ml_flags} field is a bitfield which can include the
...
@@ -221,7 +221,9 @@ The \member{ml_flags} field is a bitfield which can include the
following flags. The individual flags indicate either a calling
following flags. The individual flags indicate either a calling
convention or a binding convention. Of the calling convention flags,
convention or a binding convention. Of the calling convention flags,
only
\constant
{
METH
_
VARARGS
}
and
\constant
{
METH
_
KEYWORDS
}
can be
only
\constant
{
METH
_
VARARGS
}
and
\constant
{
METH
_
KEYWORDS
}
can be
combined. Any of the calling convention flags can be combined with a
combined (but note that
\constant
{
METH
_
KEYWORDS
}
alone is equivalent
to
\code
{
\constant
{
METH
_
VARARGS
}
|
\constant
{
METH
_
KEYWORDS
}}
).
Any of the calling convention flags can be combined with a
binding flag.
binding flag.
\begin{datadesc}
{
METH
_
VARARGS
}
\begin{datadesc}
{
METH
_
VARARGS
}
...
@@ -335,11 +337,12 @@ the definition found there:
...
@@ -335,11 +337,12 @@ the definition found there:
\verbatiminput
{
typestruct.h
}
\verbatiminput
{
typestruct.h
}
The type object structure extends the
\ctype
{
PyVarObject
}
structure,
The type object structure extends the
\ctype
{
PyVarObject
}
structure.
though it does not actually need the the
\member
{
ob
_
size
}
field. The
The
\member
{
ob
_
size
}
field is used for dynamic types (created
inclusion of this field is a historical accident that must be
by
\function
{
type
_
new()
}
, usually called from a class statement).
maintained to ensure binary compatibility between new versions of
Note that
\cdata
{
PyType
_
Type
}
(the metatype) initializes
Python and older compiled extensions.
\member
{
tp
_
itemsize
}
, which means that its instances (i.e. type
objects)
\emph
{
must
}
have the
\member
{
ob
_
size
}
field.
\begin{cmemberdesc}
{
PyObject
}{
PyObject*
}{_
ob
_
next
}
\begin{cmemberdesc}
{
PyObject
}{
PyObject*
}{_
ob
_
next
}
\cmemberline
{
PyObject
}{
PyObject*
}{_
ob
_
prev
}
\cmemberline
{
PyObject
}{
PyObject*
}{_
ob
_
prev
}
...
@@ -1488,6 +1491,7 @@ to be able to test for its presence before using it.}
...
@@ -1488,6 +1491,7 @@ to be able to test for its presence before using it.}
\begin{ctypedesc}
[getcharbufferproc]
{
int (*getcharbufferproc)
\begin{ctypedesc}
[getcharbufferproc]
{
int (*getcharbufferproc)
(PyObject *self, int segment, const char **ptrptr)
}
(PyObject *self, int segment, const char **ptrptr)
}
[Guido: the description is missing!]
\end{ctypedesc}
\end{ctypedesc}
...
...
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