# SOME DESCRIPTIVE TITLE.

# Copyright (C) 2001-2019, Python Software Foundation

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.7\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2019-05-06 11:59-0400\n"

"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

"Language-Team: LANGUAGE <LL@li.org>\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

#: ../Doc/library/ctypes.rst:2

msgid ":mod:`ctypes` --- A foreign function library for Python"

msgstr ""

#: ../Doc/library/ctypes.rst:11

msgid ""

":mod:`ctypes` is a foreign function library for Python. It provides C "

"compatible data types, and allows calling functions in DLLs or shared "

"libraries. It can be used to wrap these libraries in pure Python."

msgstr ""

#: ../Doc/library/ctypes.rst:19

msgid "ctypes tutorial"

msgstr ""

#: ../Doc/library/ctypes.rst:21

msgid ""

"Note: The code samples in this tutorial use :mod:`doctest` to make sure that "

"they actually work. Since some code samples behave differently under Linux, "

"Windows, or Mac OS X, they contain doctest directives in comments."

msgstr ""

#: ../Doc/library/ctypes.rst:25

msgid ""

"Note: Some code samples reference the ctypes :class:`c_int` type. On "

"platforms where ``sizeof(long) == sizeof(int)`` it is an alias to :class:"

"`c_long`. So, you should not be confused if :class:`c_long` is printed if "

"you would expect :class:`c_int` --- they are actually the same type."

msgstr ""

#: ../Doc/library/ctypes.rst:33

msgid "Loading dynamic link libraries"

msgstr ""

#: ../Doc/library/ctypes.rst:35

msgid ""

":mod:`ctypes` exports the *cdll*, and on Windows *windll* and *oledll* "

"objects, for loading dynamic link libraries."

msgstr ""

#: ../Doc/library/ctypes.rst:38

msgid ""

"You load libraries by accessing them as attributes of these objects. *cdll* "

"loads libraries which export functions using the standard ``cdecl`` calling "

"convention, while *windll* libraries call functions using the ``stdcall`` "

"calling convention. *oledll* also uses the ``stdcall`` calling convention, "

"and assumes the functions return a Windows :c:type:`HRESULT` error code. The "

"error code is used to automatically raise an :class:`OSError` exception when "

"the function call fails."

msgstr ""

#: ../Doc/library/ctypes.rst:46

msgid ""

"Windows errors used to raise :exc:`WindowsError`, which is now an alias of :"

"exc:`OSError`."

msgstr ""

#: ../Doc/library/ctypes.rst:51

msgid ""

"Here are some examples for Windows. Note that ``msvcrt`` is the MS standard "

"C library containing most standard C functions, and uses the cdecl calling "

"convention::"

msgstr ""

#: ../Doc/library/ctypes.rst:63

msgid "Windows appends the usual ``.dll`` file suffix automatically."

msgstr ""

#: ../Doc/library/ctypes.rst:66

msgid ""

"Accessing the standard C library through ``cdll.msvcrt`` will use an "

"outdated version of the library that may be incompatible with the one being "

"used by Python. Where possible, use native Python functionality, or else "

"import and use the ``msvcrt`` module."

msgstr ""

#: ../Doc/library/ctypes.rst:71

msgid ""

"On Linux, it is required to specify the filename *including* the extension "

"to load a library, so attribute access can not be used to load libraries. "

"Either the :meth:`LoadLibrary` method of the dll loaders should be used, or "

"you should load the library by creating an instance of CDLL by calling the "

"constructor::"

msgstr ""

#: ../Doc/library/ctypes.rst:89

msgid "Accessing functions from loaded dlls"

msgstr ""

#: ../Doc/library/ctypes.rst:91

msgid "Functions are accessed as attributes of dll objects::"

msgstr ""

#: ../Doc/library/ctypes.rst:106

msgid ""

"Note that win32 system dlls like ``kernel32`` and ``user32`` often export "

"ANSI as well as UNICODE versions of a function. The UNICODE version is "

"exported with an ``W`` appended to the name, while the ANSI version is "

"exported with an ``A`` appended to the name. The win32 ``GetModuleHandle`` "

"function, which returns a *module handle* for a given module name, has the "

"following C prototype, and a macro is used to expose one of them as "

"``GetModuleHandle`` depending on whether UNICODE is defined or not::"

msgstr ""

#: ../Doc/library/ctypes.rst:119

msgid ""

"*windll* does not try to select one of them by magic, you must access the "

"version you need by specifying ``GetModuleHandleA`` or ``GetModuleHandleW`` "

"explicitly, and then call it with bytes or string objects respectively."

msgstr ""

#: ../Doc/library/ctypes.rst:123

msgid ""

"Sometimes, dlls export functions with names which aren't valid Python "

"identifiers, like ``\"??2@YAPAXI@Z\"``. In this case you have to use :func:"

"`getattr` to retrieve the function::"

msgstr ""

#: ../Doc/library/ctypes.rst:131

msgid ""

"On Windows, some dlls export functions not by name but by ordinal. These "

"functions can be accessed by indexing the dll object with the ordinal "

"number::"

msgstr ""

#: ../Doc/library/ctypes.rst:148

msgid "Calling functions"

msgstr ""

#: ../Doc/library/ctypes.rst:150

msgid ""

"You can call these functions like any other Python callable. This example "

"uses the ``time()`` function, which returns system time in seconds since the "

"Unix epoch, and the ``GetModuleHandleA()`` function, which returns a win32 "

"module handle."

msgstr ""

#: ../Doc/library/ctypes.rst:155

msgid ""

"This example calls both functions with a NULL pointer (``None`` should be "

"used as the NULL pointer)::"

msgstr ""

#: ../Doc/library/ctypes.rst:166

msgid ""

":mod:`ctypes` may raise a :exc:`ValueError` after calling the function, if "

"it detects that an invalid number of arguments were passed. This behavior "

"should not be relied upon. It is deprecated in 3.6.2, and will be removed "

"in 3.7."

msgstr ""

#: ../Doc/library/ctypes.rst:171

msgid ""

":exc:`ValueError` is raised when you call an ``stdcall`` function with the "

"``cdecl`` calling convention, or vice versa::"

msgstr ""

#: ../Doc/library/ctypes.rst:186

msgid ""

"To find out the correct calling convention you have to look into the C "

"header file or the documentation for the function you want to call."

msgstr ""

#: ../Doc/library/ctypes.rst:189

msgid ""

"On Windows, :mod:`ctypes` uses win32 structured exception handling to "

"prevent crashes from general protection faults when functions are called "

"with invalid argument values::"

msgstr ""

#: ../Doc/library/ctypes.rst:199

msgid ""

"There are, however, enough ways to crash Python with :mod:`ctypes`, so you "

"should be careful anyway. The :mod:`faulthandler` module can be helpful in "

"debugging crashes (e.g. from segmentation faults produced by erroneous C "

"library calls)."

msgstr ""

#: ../Doc/library/ctypes.rst:204

msgid ""

"``None``, integers, bytes objects and (unicode) strings are the only native "

"Python objects that can directly be used as parameters in these function "

"calls. ``None`` is passed as a C ``NULL`` pointer, bytes objects and strings "

"are passed as pointer to the memory block that contains their data (:c:type:"

"`char *` or :c:type:`wchar_t *`). Python integers are passed as the "

"platforms default C :c:type:`int` type, their value is masked to fit into "

"the C type."

msgstr ""

#: ../Doc/library/ctypes.rst:211

msgid ""

"Before we move on calling functions with other parameter types, we have to "

"learn more about :mod:`ctypes` data types."

msgstr ""

#: ../Doc/library/ctypes.rst:218 ../Doc/library/ctypes.rst:2066

msgid "Fundamental data types"

msgstr ""

#: ../Doc/library/ctypes.rst:220

msgid ":mod:`ctypes` defines a number of primitive C compatible data types:"

msgstr ""

#: ../Doc/library/ctypes.rst:223

msgid "ctypes type"

msgstr ""

#: ../Doc/library/ctypes.rst:223

msgid "C type"

msgstr ""

#: ../Doc/library/ctypes.rst:223

msgid "Python type"

msgstr ""

#: ../Doc/library/ctypes.rst:225

msgid ":class:`c_bool`"

msgstr ""

#: ../Doc/library/ctypes.rst:225

msgid ":c:type:`_Bool`"

msgstr ""

#: ../Doc/library/ctypes.rst:225

msgid "bool (1)"

msgstr ""

#: ../Doc/library/ctypes.rst:227

msgid ":class:`c_char`"

msgstr ""

#: ../Doc/library/ctypes.rst:227 ../Doc/library/ctypes.rst:231

msgid ":c:type:`char`"

msgstr ""

#: ../Doc/library/ctypes.rst:227

msgid "1-character bytes object"

msgstr ""

#: ../Doc/library/ctypes.rst:229

msgid ":class:`c_wchar`"

msgstr ""

#: ../Doc/library/ctypes.rst:229

msgid ":c:type:`wchar_t`"

msgstr ""

#: ../Doc/library/ctypes.rst:229

msgid "1-character string"

msgstr ""

#: ../Doc/library/ctypes.rst:231

msgid ":class:`c_byte`"

msgstr ""

#: ../Doc/library/ctypes.rst:231 ../Doc/library/ctypes.rst:233

#: ../Doc/library/ctypes.rst:235 ../Doc/library/ctypes.rst:237

#: ../Doc/library/ctypes.rst:239 ../Doc/library/ctypes.rst:241

#: ../Doc/library/ctypes.rst:243 ../Doc/library/ctypes.rst:245

#: ../Doc/library/ctypes.rst:247 ../Doc/library/ctypes.rst:249

#: ../Doc/library/ctypes.rst:252 ../Doc/library/ctypes.rst:254

msgid "int"

msgstr ""

#: ../Doc/library/ctypes.rst:233

msgid ":class:`c_ubyte`"

msgstr ""

#: ../Doc/library/ctypes.rst:233

msgid ":c:type:`unsigned char`"

msgstr ""

#: ../Doc/library/ctypes.rst:235

msgid ":class:`c_short`"

msgstr ""

#: ../Doc/library/ctypes.rst:235

msgid ":c:type:`short`"

msgstr ""

#: ../Doc/library/ctypes.rst:237

msgid ":class:`c_ushort`"

msgstr ""

#: ../Doc/library/ctypes.rst:237

msgid ":c:type:`unsigned short`"

msgstr ""

#: ../Doc/library/ctypes.rst:239

msgid ":class:`c_int`"

msgstr ""

#: ../Doc/library/ctypes.rst:239

msgid ":c:type:`int`"

msgstr ""

#: ../Doc/library/ctypes.rst:241

msgid ":class:`c_uint`"

msgstr ""

#: ../Doc/library/ctypes.rst:241

msgid ":c:type:`unsigned int`"

msgstr ""

#: ../Doc/library/ctypes.rst:243

msgid ":class:`c_long`"

msgstr ""

#: ../Doc/library/ctypes.rst:243

msgid ":c:type:`long`"

msgstr ""

#: ../Doc/library/ctypes.rst:245

msgid ":class:`c_ulong`"

msgstr ""

#: ../Doc/library/ctypes.rst:245

msgid ":c:type:`unsigned long`"

msgstr ""

#: ../Doc/library/ctypes.rst:247

msgid ":class:`c_longlong`"

msgstr ""

#: ../Doc/library/ctypes.rst:247

msgid ":c:type:`__int64` or :c:type:`long long`"

msgstr ""

#: ../Doc/library/ctypes.rst:249

msgid ":class:`c_ulonglong`"

msgstr ""

#: ../Doc/library/ctypes.rst:249

msgid ":c:type:`unsigned __int64` or :c:type:`unsigned long long`"

msgstr ""

#: ../Doc/library/ctypes.rst:252

msgid ":class:`c_size_t`"

msgstr ""

#: ../Doc/library/ctypes.rst:252

msgid ":c:type:`size_t`"

msgstr ""

#: ../Doc/library/ctypes.rst:254

msgid ":class:`c_ssize_t`"

msgstr ""

#: ../Doc/library/ctypes.rst:254

msgid ":c:type:`ssize_t` or :c:type:`Py_ssize_t`"

msgstr ""

#: ../Doc/library/ctypes.rst:257

msgid ":class:`c_float`"

msgstr ""

#: ../Doc/library/ctypes.rst:257

msgid ":c:type:`float`"

msgstr ""

#: ../Doc/library/ctypes.rst:257 ../Doc/library/ctypes.rst:259

#: ../Doc/library/ctypes.rst:261

msgid "float"

msgstr ""

#: ../Doc/library/ctypes.rst:259

msgid ":class:`c_double`"

msgstr ""

#: ../Doc/library/ctypes.rst:259

msgid ":c:type:`double`"

msgstr ""

#: ../Doc/library/ctypes.rst:261

msgid ":class:`c_longdouble`"

msgstr ""

#: ../Doc/library/ctypes.rst:261

msgid ":c:type:`long double`"

msgstr ""

#: ../Doc/library/ctypes.rst:263

msgid ":class:`c_char_p`"

msgstr ""

#: ../Doc/library/ctypes.rst:263

msgid ":c:type:`char *` (NUL terminated)"

msgstr ""

#: ../Doc/library/ctypes.rst:263

msgid "bytes object or ``None``"

msgstr ""

#: ../Doc/library/ctypes.rst:265

msgid ":class:`c_wchar_p`"

msgstr ""

#: ../Doc/library/ctypes.rst:265

msgid ":c:type:`wchar_t *` (NUL terminated)"

msgstr ""

#: ../Doc/library/ctypes.rst:265

msgid "string or ``None``"

msgstr ""

#: ../Doc/library/ctypes.rst:267

msgid ":class:`c_void_p`"

msgstr ""

#: ../Doc/library/ctypes.rst:267

msgid ":c:type:`void *`"

msgstr ""

#: ../Doc/library/ctypes.rst:267

msgid "int or ``None``"

msgstr ""

#: ../Doc/library/ctypes.rst:271

msgid "The constructor accepts any object with a truth value."

msgstr ""

#: ../Doc/library/ctypes.rst:273

msgid ""

"All these types can be created by calling them with an optional initializer "

"of the correct type and value::"

msgstr ""

#: ../Doc/library/ctypes.rst:284

msgid ""

"Since these types are mutable, their value can also be changed afterwards::"

msgstr ""

#: ../Doc/library/ctypes.rst:296

msgid ""

"Assigning a new value to instances of the pointer types :class:`c_char_p`, :"

"class:`c_wchar_p`, and :class:`c_void_p` changes the *memory location* they "

"point to, *not the contents* of the memory block (of course not, because "

"Python bytes objects are immutable)::"

msgstr ""

#: ../Doc/library/ctypes.rst:316

msgid ""

"You should be careful, however, not to pass them to functions expecting "

"pointers to mutable memory. If you need mutable memory blocks, ctypes has a :"

"func:`create_string_buffer` function which creates these in various ways. "

"The current memory block contents can be accessed (or changed) with the "

"``raw`` property; if you want to access it as NUL terminated string, use the "

"``value`` property::"

msgstr ""

#: ../Doc/library/ctypes.rst:340

msgid ""

"The :func:`create_string_buffer` function replaces the :func:`c_buffer` "

"function (which is still available as an alias), as well as the :func:"

"`c_string` function from earlier ctypes releases. To create a mutable "

"memory block containing unicode characters of the C type :c:type:`wchar_t` "

"use the :func:`create_unicode_buffer` function."

msgstr ""

#: ../Doc/library/ctypes.rst:350

msgid "Calling functions, continued"

msgstr ""

#: ../Doc/library/ctypes.rst:352

msgid ""

"Note that printf prints to the real standard output channel, *not* to :data:"

"`sys.stdout`, so these examples will only work at the console prompt, not "

"from within *IDLE* or *PythonWin*::"

msgstr ""

#: ../Doc/library/ctypes.rst:372

msgid ""

"As has been mentioned before, all Python types except integers, strings, and "

"bytes objects have to be wrapped in their corresponding :mod:`ctypes` type, "

"so that they can be converted to the required C data type::"

msgstr ""

#: ../Doc/library/ctypes.rst:385

msgid "Calling functions with your own custom data types"

msgstr ""

#: ../Doc/library/ctypes.rst:387

msgid ""

"You can also customize :mod:`ctypes` argument conversion to allow instances "

"of your own classes be used as function arguments. :mod:`ctypes` looks for "

"an :attr:`_as_parameter_` attribute and uses this as the function argument. "

"Of course, it must be one of integer, string, or bytes::"

msgstr ""

#: ../Doc/library/ctypes.rst:402

msgid ""

"If you don't want to store the instance's data in the :attr:`_as_parameter_` "

"instance variable, you could define a :class:`property` which makes the "

"attribute available on request."

msgstr ""

#: ../Doc/library/ctypes.rst:410

msgid "Specifying the required argument types (function prototypes)"

msgstr ""

#: ../Doc/library/ctypes.rst:412

msgid ""

"It is possible to specify the required argument types of functions exported "

"from DLLs by setting the :attr:`argtypes` attribute."

msgstr ""

#: ../Doc/library/ctypes.rst:415

msgid ""

":attr:`argtypes` must be a sequence of C data types (the ``printf`` function "

"is probably not a good example here, because it takes a variable number and "

"different types of parameters depending on the format string, on the other "

"hand this is quite handy to experiment with this feature)::"

msgstr ""

#: ../Doc/library/ctypes.rst:426

msgid ""

"Specifying a format protects against incompatible argument types (just as a "

"prototype for a C function), and tries to convert the arguments to valid "

"types::"

msgstr ""

#: ../Doc/library/ctypes.rst:438

msgid ""

"If you have defined your own classes which you pass to function calls, you "

"have to implement a :meth:`from_param` class method for them to be able to "

"use them in the :attr:`argtypes` sequence. The :meth:`from_param` class "

"method receives the Python object passed to the function call, it should do "

"a typecheck or whatever is needed to make sure this object is acceptable, "

"and then return the object itself, its :attr:`_as_parameter_` attribute, or "

"whatever you want to pass as the C function argument in this case. Again, "

"the result should be an integer, string, bytes, a :mod:`ctypes` instance, or "

"an object with an :attr:`_as_parameter_` attribute."

msgstr ""

#: ../Doc/library/ctypes.rst:452

msgid "Return types"

msgstr ""

#: ../Doc/library/ctypes.rst:454

msgid ""

"By default functions are assumed to return the C :c:type:`int` type. Other "

"return types can be specified by setting the :attr:`restype` attribute of "

"the function object."

msgstr ""

#: ../Doc/library/ctypes.rst:458

msgid ""

"Here is a more advanced example, it uses the ``strchr`` function, which "

"expects a string pointer and a char, and returns a pointer to a string::"

msgstr ""

#: ../Doc/library/ctypes.rst:471

msgid ""

"If you want to avoid the ``ord(\"x\")`` calls above, you can set the :attr:"

"`argtypes` attribute, and the second argument will be converted from a "

"single character Python bytes object into a C char::"

msgstr ""

#: ../Doc/library/ctypes.rst:489

msgid ""

"You can also use a callable Python object (a function or a class for "

"example) as the :attr:`restype` attribute, if the foreign function returns "

"an integer. The callable will be called with the *integer* the C function "

"returns, and the result of this call will be used as the result of your "

"function call. This is useful to check for error return values and "

"automatically raise an exception::"

msgstr ""

#: ../Doc/library/ctypes.rst:512

msgid ""

"``WinError`` is a function which will call Windows ``FormatMessage()`` api "

"to get the string representation of an error code, and *returns* an "

"exception. ``WinError`` takes an optional error code parameter, if no one is "

"used, it calls :func:`GetLastError` to retrieve it."

msgstr ""

#: ../Doc/library/ctypes.rst:517

msgid ""

"Please note that a much more powerful error checking mechanism is available "

"through the :attr:`errcheck` attribute; see the reference manual for details."

msgstr ""

#: ../Doc/library/ctypes.rst:524

msgid "Passing pointers (or: passing parameters by reference)"

msgstr ""

#: ../Doc/library/ctypes.rst:526

msgid ""

"Sometimes a C api function expects a *pointer* to a data type as parameter, "

"probably to write into the corresponding location, or if the data is too "

"large to be passed by value. This is also known as *passing parameters by "

"reference*."

msgstr ""

#: ../Doc/library/ctypes.rst:530

msgid ""

":mod:`ctypes` exports the :func:`byref` function which is used to pass "

"parameters by reference. The same effect can be achieved with the :func:"

"`pointer` function, although :func:`pointer` does a lot more work since it "

"constructs a real pointer object, so it is faster to use :func:`byref` if "

"you don't need the pointer object in Python itself::"

msgstr ""

#: ../Doc/library/ctypes.rst:552

msgid "Structures and unions"

msgstr ""

#: ../Doc/library/ctypes.rst:554

msgid ""

"Structures and unions must derive from the :class:`Structure` and :class:"

"`Union` base classes which are defined in the :mod:`ctypes` module. Each "

"subclass must define a :attr:`_fields_` attribute. :attr:`_fields_` must be "

"a list of *2-tuples*, containing a *field name* and a *field type*."

msgstr ""

#: ../Doc/library/ctypes.rst:559

msgid ""

"The field type must be a :mod:`ctypes` type like :class:`c_int`, or any "

"other derived :mod:`ctypes` type: structure, union, array, pointer."

msgstr ""

#: ../Doc/library/ctypes.rst:562

msgid ""

"Here is a simple example of a POINT structure, which contains two integers "

"named *x* and *y*, and also shows how to initialize a structure in the "

"constructor::"

msgstr ""

#: ../Doc/library/ctypes.rst:582

msgid ""

"You can, however, build much more complicated structures. A structure can "

"itself contain other structures by using a structure as a field type."

msgstr ""

#: ../Doc/library/ctypes.rst:585

msgid ""

"Here is a RECT structure which contains two POINTs named *upperleft* and "

"*lowerright*::"

msgstr ""

#: ../Doc/library/ctypes.rst:599

msgid ""

"Nested structures can also be initialized in the constructor in several "

"ways::"

msgstr ""

#: ../Doc/library/ctypes.rst:604

msgid ""

"Field :term:`descriptor`\\s can be retrieved from the *class*, they are "

"useful for debugging because they can provide useful information::"

msgstr ""

#: ../Doc/library/ctypes.rst:618

msgid ""

":mod:`ctypes` does not support passing unions or structures with bit-fields "

"to functions by value. While this may work on 32-bit x86, it's not "

"guaranteed by the library to work in the general case. Unions and "

"structures with bit-fields should always be passed to functions by pointer."

msgstr ""

#: ../Doc/library/ctypes.rst:624

msgid "Structure/union alignment and byte order"

msgstr ""

#: ../Doc/library/ctypes.rst:626

msgid ""

"By default, Structure and Union fields are aligned in the same way the C "

"compiler does it. It is possible to override this behavior be specifying a :"

"attr:`_pack_` class attribute in the subclass definition. This must be set "

"to a positive integer and specifies the maximum alignment for the fields. "

"This is what ``#pragma pack(n)`` also does in MSVC."

msgstr ""

#: ../Doc/library/ctypes.rst:632

msgid ""

":mod:`ctypes` uses the native byte order for Structures and Unions. To "

"build structures with non-native byte order, you can use one of the :class:"

"`BigEndianStructure`, :class:`LittleEndianStructure`, :class:"

"`BigEndianUnion`, and :class:`LittleEndianUnion` base classes. These "

"classes cannot contain pointer fields."

msgstr ""

#: ../Doc/library/ctypes.rst:642

msgid "Bit fields in structures and unions"

msgstr ""

#: ../Doc/library/ctypes.rst:644

msgid ""

"It is possible to create structures and unions containing bit fields. Bit "

"fields are only possible for integer fields, the bit width is specified as "

"the third item in the :attr:`_fields_` tuples::"

msgstr ""

#: ../Doc/library/ctypes.rst:662

msgid "Arrays"

msgstr ""

#: ../Doc/library/ctypes.rst:664

msgid ""

"Arrays are sequences, containing a fixed number of instances of the same "

"type."

msgstr ""

#: ../Doc/library/ctypes.rst:666

msgid ""

"The recommended way to create array types is by multiplying a data type with "

"a positive integer::"

msgstr ""

#: ../Doc/library/ctypes.rst:671

msgid ""

"Here is an example of a somewhat artificial data type, a structure "

"containing 4 POINTs among other stuff::"

msgstr ""

#: ../Doc/library/ctypes.rst:687

msgid "Instances are created in the usual way, by calling the class::"

msgstr ""

#: ../Doc/library/ctypes.rst:693

msgid ""

"The above code print a series of ``0 0`` lines, because the array contents "

"is initialized to zeros."

msgstr ""

#: ../Doc/library/ctypes.rst:696

msgid "Initializers of the correct type can also be specified::"

msgstr ""

#: ../Doc/library/ctypes.rst:712

msgid "Pointers"

msgstr ""

#: ../Doc/library/ctypes.rst:714

msgid ""

"Pointer instances are created by calling the :func:`pointer` function on a :"

"mod:`ctypes` type::"

msgstr ""

#: ../Doc/library/ctypes.rst:722

msgid ""

"Pointer instances have a :attr:`~_Pointer.contents` attribute which returns "

"the object to which the pointer points, the ``i`` object above::"

msgstr ""

#: ../Doc/library/ctypes.rst:729

msgid ""

"Note that :mod:`ctypes` does not have OOR (original object return), it "

"constructs a new, equivalent object each time you retrieve an attribute::"

msgstr ""

#: ../Doc/library/ctypes.rst:738

msgid ""

"Assigning another :class:`c_int` instance to the pointer's contents "

"attribute would cause the pointer to point to the memory location where this "

"is stored::"

msgstr ""

#: ../Doc/library/ctypes.rst:750

msgid "Pointer instances can also be indexed with integers::"

msgstr ""

#: ../Doc/library/ctypes.rst:756

msgid "Assigning to an integer index changes the pointed to value::"

msgstr ""

#: ../Doc/library/ctypes.rst:765

msgid ""

"It is also possible to use indexes different from 0, but you must know what "

"you're doing, just as in C: You can access or change arbitrary memory "

"locations. Generally you only use this feature if you receive a pointer from "

"a C function, and you *know* that the pointer actually points to an array "

"instead of a single item."

msgstr ""

#: ../Doc/library/ctypes.rst:771

msgid ""

"Behind the scenes, the :func:`pointer` function does more than simply create "

"pointer instances, it has to create pointer *types* first. This is done with "

"the :func:`POINTER` function, which accepts any :mod:`ctypes` type, and "

"returns a new type::"

msgstr ""

#: ../Doc/library/ctypes.rst:787

msgid ""

"Calling the pointer type without an argument creates a ``NULL`` pointer. "

"``NULL`` pointers have a ``False`` boolean value::"

msgstr ""

#: ../Doc/library/ctypes.rst:795

msgid ""

":mod:`ctypes` checks for ``NULL`` when dereferencing pointers (but "

"dereferencing invalid non-\\ ``NULL`` pointers would crash Python)::"

msgstr ""

#: ../Doc/library/ctypes.rst:814

msgid "Type conversions"

msgstr ""

#: ../Doc/library/ctypes.rst:816

msgid ""

"Usually, ctypes does strict type checking. This means, if you have "

"``POINTER(c_int)`` in the :attr:`argtypes` list of a function or as the type "

"of a member field in a structure definition, only instances of exactly the "

"same type are accepted. There are some exceptions to this rule, where "

"ctypes accepts other objects. For example, you can pass compatible array "

"instances instead of pointer types. So, for ``POINTER(c_int)``, ctypes "

"accepts an array of c_int::"

msgstr ""

#: ../Doc/library/ctypes.rst:837

msgid ""

"In addition, if a function argument is explicitly declared to be a pointer "

"type (such as ``POINTER(c_int)``) in :attr:`argtypes`, an object of the "

"pointed type (``c_int`` in this case) can be passed to the function. ctypes "

"will apply the required :func:`byref` conversion in this case automatically."

msgstr ""

#: ../Doc/library/ctypes.rst:842

msgid "To set a POINTER type field to ``NULL``, you can assign ``None``::"

msgstr ""

#: ../Doc/library/ctypes.rst:849

msgid ""

"Sometimes you have instances of incompatible types. In C, you can cast one "

"type into another type. :mod:`ctypes` provides a :func:`cast` function "

"which can be used in the same way. The ``Bar`` structure defined above "

"accepts ``POINTER(c_int)`` pointers or :class:`c_int` arrays for its "

"``values`` field, but not instances of other types::"

msgstr ""

#: ../Doc/library/ctypes.rst:861

msgid "For these cases, the :func:`cast` function is handy."

msgstr ""

#: ../Doc/library/ctypes.rst:863

msgid ""

"The :func:`cast` function can be used to cast a ctypes instance into a "

"pointer to a different ctypes data type. :func:`cast` takes two parameters, "

"a ctypes object that is or can be converted to a pointer of some kind, and a "

"ctypes pointer type. It returns an instance of the second argument, which "

"references the same memory block as the first argument::"

msgstr ""

#: ../Doc/library/ctypes.rst:874

msgid ""

"So, :func:`cast` can be used to assign to the ``values`` field of ``Bar`` "

"the structure::"

msgstr ""

#: ../Doc/library/ctypes.rst:887

msgid "Incomplete Types"

msgstr ""

#: ../Doc/library/ctypes.rst:889

msgid ""

"*Incomplete Types* are structures, unions or arrays whose members are not "

"yet specified. In C, they are specified by forward declarations, which are "

"defined later::"

msgstr ""

#: ../Doc/library/ctypes.rst:900

msgid ""

"The straightforward translation into ctypes code would be this, but it does "

"not work::"

msgstr ""

#: ../Doc/library/ctypes.rst:913

msgid ""

"because the new ``class cell`` is not available in the class statement "

"itself. In :mod:`ctypes`, we can define the ``cell`` class and set the :attr:"

"`_fields_` attribute later, after the class statement::"

msgstr ""

#: ../Doc/library/ctypes.rst:925

msgid ""

"Lets try it. We create two instances of ``cell``, and let them point to each "

"other, and finally follow the pointer chain a few times::"

msgstr ""

#: ../Doc/library/ctypes.rst:946

msgid "Callback functions"

msgstr ""

#: ../Doc/library/ctypes.rst:948

msgid ""

":mod:`ctypes` allows creating C callable function pointers from Python "

"callables. These are sometimes called *callback functions*."

msgstr ""

#: ../Doc/library/ctypes.rst:951

msgid ""

"First, you must create a class for the callback function. The class knows "

"the calling convention, the return type, and the number and types of "

"arguments this function will receive."

msgstr ""

#: ../Doc/library/ctypes.rst:955

msgid ""

"The :func:`CFUNCTYPE` factory function creates types for callback functions "

"using the ``cdecl`` calling convention. On Windows, the :func:`WINFUNCTYPE` "

"factory function creates types for callback functions using the ``stdcall`` "

"calling convention."

msgstr ""

#: ../Doc/library/ctypes.rst:960

msgid ""

"Both of these factory functions are called with the result type as first "

"argument, and the callback functions expected argument types as the "

"remaining arguments."

msgstr ""

#: ../Doc/library/ctypes.rst:964

msgid ""

"I will present an example here which uses the standard C library's :c:func:"

"`qsort` function, that is used to sort items with the help of a callback "

"function. :c:func:`qsort` will be used to sort an array of integers::"

msgstr ""

#: ../Doc/library/ctypes.rst:974

msgid ""

":func:`qsort` must be called with a pointer to the data to sort, the number "

"of items in the data array, the size of one item, and a pointer to the "

"comparison function, the callback. The callback will then be called with two "

"pointers to items, and it must return a negative integer if the first item "

"is smaller than the second, a zero if they are equal, and a positive integer "

"otherwise."

msgstr ""

#: ../Doc/library/ctypes.rst:980

msgid ""

"So our callback function receives pointers to integers, and must return an "

"integer. First we create the ``type`` for the callback function::"

msgstr ""

#: ../Doc/library/ctypes.rst:986

msgid ""

"To get started, here is a simple callback that shows the values it gets "

"passed::"

msgstr ""

#: ../Doc/library/ctypes.rst:996

msgid "The result::"

msgstr ""

#: ../Doc/library/ctypes.rst:1006

msgid "Now we can actually compare the two items and return a useful result::"

msgstr ""

#: ../Doc/library/ctypes.rst:1021

msgid "As we can easily check, our array is sorted now::"

msgstr ""

#: ../Doc/library/ctypes.rst:1028

msgid ""

"The function factories can be used as decorator factories, so we may as well "

"write::"

msgstr ""

#: ../Doc/library/ctypes.rst:1046

msgid ""

"Make sure you keep references to :func:`CFUNCTYPE` objects as long as they "

"are used from C code. :mod:`ctypes` doesn't, and if you don't, they may be "

"garbage collected, crashing your program when a callback is made."

msgstr ""

#: ../Doc/library/ctypes.rst:1050

msgid ""

"Also, note that if the callback function is called in a thread created "

"outside of Python's control (e.g. by the foreign code that calls the "

"callback), ctypes creates a new dummy Python thread on every invocation. "

"This behavior is correct for most purposes, but it means that values stored "

"with :class:`threading.local` will *not* survive across different callbacks, "

"even when those calls are made from the same C thread."

msgstr ""

#: ../Doc/library/ctypes.rst:1060

msgid "Accessing values exported from dlls"

msgstr ""

#: ../Doc/library/ctypes.rst:1062

msgid ""