I have a function that will be implemented in an extension:
ZEND_FUNCTION(msr_set_time);
which started life as a real C function:
void msr_set_time( const time_t ts );
I'm using Andrei's way, zend_parse_parameters(), to handle arguments. So,
long l;
zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "l", &l);
seems to make sense. But, what if my code ends up on a platform where time_t
is an int? Essentially, the question is how to use compiler specific
typedefs with zend_parse_parameters()
Thank you,
Hans
I have a function that will be implemented in an extension:
ZEND_FUNCTION(msr_set_time);
which started life as a real C function:
void msr_set_time( const time_t ts );
I'm using Andrei's way, zend_parse_parameters(), to handle arguments. So,
long l;
zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "l", &l);seems to make sense. But, what if my code ends up on a platform where time_t
is an int? Essentially, the question is how to use compiler specific
typedefs with zend_parse_parameters()
well you could register a resource, but a long is fine. Just cast it to
a time_t when you pass it. You shouldn't have to worry about overflows.
-Sterling
Thank you,
Hans
--
Good judgement comes from experience, and experience comes from
bad judgement.
- Fred Brooks