Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:1452
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Hans Zaunere <hans@nyphp.org>
Cc: internals@lists.php.net
In-Reply-To: <20030512182902.34209.qmail@web12806.mail.yahoo.com>
References: <20030512182902.34209.qmail@web12806.mail.yahoo.com>
Content-Type: text/plain
Organization: 
Message-ID: <1052761164.6733.59.camel@hasele>
Mime-Version: 1.0
Date: 12 May 2003 13:39:24 -0400
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Accepting time_t as an argument
From: sterling@bumblebury.com (Sterling Hughes)

On Mon, 2003-05-12 at 14:29, Hans Zaunere wrote:
> 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