diff --git a/internals/zendapi/variables.xml b/internals/zendapi/variables.xml index e5db91719d..dbe1126656 100644 --- a/internals/zendapi/variables.xml +++ b/internals/zendapi/variables.xml @@ -1,5 +1,5 @@ - + Creating Variables @@ -472,7 +472,7 @@ The index is always an integer. add_index_stringl(zval *array, uint idx, char *str, uint length, int duplicate); Adds a string with the desired - length length to the array. This function is faster and binary-safe. Otherwise, behaves like add_index_string(). + length length to the array. This function is faster and binary-safe. Otherwise, behaves like add_index_string. add_index_zval(zval *array, uint idx, zval *value); @@ -533,7 +533,7 @@ These functions automatically generate a new index based on the highest index fo add_next_index_stringl(zval *array, char *str, uint length, int duplicate); Adds a string with the desired - length length to the array. This function is faster and binary-safe. Otherwise, behaves like add_index_string(). + length length to the array. This function is faster and binary-safe. Otherwise, behaves like add_index_string. add_next_index_zval(zval *array, zval *value); @@ -546,7 +546,7 @@ These functions automatically generate a new index based on the highest index fo All these functions provide a handy abstraction to Zend's internal hash API. Of course, you can also use the hash functions directly - for example, if you already have a zval container allocated that you want to - insert into an array. This is done using zend_hash_update() + insert into an array. This is done using zend_hash_update for associative arrays (see ) and zend_hash_index_update for indexed arrays (see ): @@ -951,7 +951,7 @@ int ZEND_REGISTER_RESOURCE(zval *rsrc_result, void *rsrc_pointer, int rsrc_type) return rsrc_id; - The returned rsrc_id uniquly identifies the newly + The returned rsrc_id uniquely identifies the newly registered resource. You can use the macro RETURN_RESOURE to return it to the user: RETURN_RESOURCE(rsrc_id)