You searched for: declaration (Koreanska - Engelska)

public identifier of the external notation declaration.
instead of a function name, an array containing an object reference and a method name can also be supplied.

예 31-1. internal declaration of zend_function_entry.
typedef struct _zend_function_entry {char *fname; void (*handler)(internal_function_parameters); unsigned char *func_arg_types;} zend_function_entry;

c declaration of exported functions (required to declare the zend function block)
declaration of the zend module block

a notation declaration is part of the document's dtd and has the following format:
!notation name {system_id _bar_ public_id}

this handler will be called if the xml parser encounters an external entity declaration with an ndata declaration, like the following:
!entity name {publicid _bar_ systemid} ndata notationname

to return a reference from a function, you have to use the reference operator in both the function declaration and when assigning the returned value to a variable:
to return a reference from a function, you have to use the reference operator in both the function declaration and when assigning the returned value to a variable:

this is the base for resolving the system identifier (systemid) of the notation declaration. currently this parameter will always be set to an empty string.
if a handler function is set to an empty string, or false, the handler in question is disabled.

declaration and implementation of these functions can be done with macros; see the earlier section "declaration of the zend module block" for details.
prev

sets the notation declaration handler function for the xml parser parser. handler is a string containing the name of a function that must exist when xml_parse() is called for parser.
sets the external entity reference handler function for the xml parser parser. handler is a string containing the name of a function that must exist when xml_parse() is called for parser.

sets the namespace of a node to uri. if there is already a namespace declaration with the same uri in one of the parent nodes of the node, the prefix of this is taken, otherwise it will take the one provided in the optional parameter prefix or generate a random one.
if there is already a namespace declaration with the same uri in one of the parent nodes of the node, the prefix of this is taken, otherwise it will take the one provided in the optional parameter prefix or generate a random one.

after the declaration, code for checking and retrieving the function's arguments, argument conversion, and return value generation follows (more on this later).
after the declaration, code for checking and retrieving the function' s arguments, argument conversion, and return value generation follows (more on this later).

for reference purposes, you can find a list of the macros involved in declared startup and shutdown functions in 표 31-3. these are not used in our basic example yet, but will be demonstrated later on. you should make use of these macros to declare your startup and shutdown functions, as these require special arguments to be passed (init_func_args and shutdown_func_args), which are automatically included into the function declaration when using the predefined macros. if you declare your functions manually and the php developers decide that a change in the argument list is necessary, you'll have to change your module sources to remain compatible.
if you declare your functions manually and the php developers decide that a change in the argument list is necessary, you 'll have to change your module sources to remain compatible.