Usted buscó: destructor (Inglés - Coreano)

(destructor)
(제거자)

ditylenchus destructor
감자썩이선충

the copy constructor' s counterpart in the zend api, the destructor zval_dtor(), does the opposite of the constructor.
the copy constructor's counterpart in the zend api, the destructor zval_dtor(), does the opposite of the constructor.

the one in the persistent list destructor should properly free any resources obtained by that type (e.g. memory, sql links, etc).
when you register a resource that's going to be in the persistent list, you should add destructors to it both in the non-persistent list and in the persistent list. the destructor in the non-persistent list destructor shouldn't do anything. the one in the persistent list destructor should properly free any resources obtained by that type (e.g. memory, sql links, etc). just like with the non-persistent resources, you *must* add destructors for every resource, even it requires no destructotion and the destructor would be empty. remember, since emalloc() and friends aren't to be used in conjunction with the persistent list, you mustn't use efree() here either.

note the use of the constructor and destructor calls at the end - it might not be necessary to do it this way here (since they should be separate values, the assignment might be safe), but this is bulletproof.
예 38-1 shows a small demonstration of calling a user function. the code calls a function that's supplied to it as argument and directly passes this function's return value through as its own return value. note the use of the constructor and destructor calls at the end - it might not be necessary to do it this way here (since they should be separate values, the assignment might be safe), but this is bulletproof.