Re: cvs: php-src /ext/date config.m4 php_date.c /ext/date/lib .cvsignore dow.c parse_date.c parse_tz.c timelib.c timelib.h
timelib.m4 timelib_structs.h tm2unixtime.c unixtime2tm.c /ext/date/lib/resource parse_date.re

From: Date: Fri, 17 Jun 2005 00:22:57 +0000
Subject: Re: cvs: php-src /ext/date config.m4 php_date.c /ext/date/lib .cvsignore dow.c parse_date.c parse_tz.c timelib.c timelib.h
timelib.m4 timelib_structs.h tm2unixtime.c unixtime2tm.c /ext/date/lib/resource parse_date.re
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-16767@lists.php.net to get a copy of this message
On Thu, 16 Jun 2005 23:12:11 -0000 sniper@php.net ("Jani Taskinen") wrote: > sniper Thu Jun 16 19:12:11 2005 EDT > > Added files: > /php-src/ext/date/lib timelib.m4 > > Modified files: > /php-src/ext/date config.m4 php_date.c > /php-src/ext/date/lib .cvsignore dow.c parse_date.c > parse_tz.c timelib.c timelib.h timelib_structs.h > tm2unixtime.c unixtime2tm.c > /php-src/ext/date/lib/resource parse_date.re > Log: > - Improve portability. > # TODO: The standalone lib needs it's own build stuff, pretty > # much same as Zend has for standalone builds. Why not use the same as I did in pecl/date? I understand to split some functions in separate files but why a lib for something that will always be included? For the TZ datas, a lib makes sense though, easier to update only the TZ datas between PHP releases. --Pierre

« previous php.internals (#16767) next »