[PHP-DEV] [Spam 05.31] RE: [PHP-DEV] Inheriting from internal classes

2004-05-14 Thread Wez Furlong
Spam detection software, running on the system "jc.thebrainroom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or block similar future email. If you have any questions, see the administrator of that s

[PHP-DEV] Inheriting from internal classes

2004-05-14 Thread l0t3k
Wez and Marcus (and anyone else), is there a way with the current CVS to permit subclassing of internal, overloaded classes without seg faulting ? or is this a known problem. i ask this based on my reading of the source for PDO. l0t3k -- PHP Internals - PHP Runtime Development Mailing List To

Re: [PHP-DEV] Type hints resolution?

2004-05-14 Thread Marcus Boerger
Hello Hans, Friday, May 14, 2004, 4:53:44 PM, you wrote: > Hi, > I just wanted to find out what the final resolution was on the typehints > discussion for RC3. I know that I (& others) will be sad to see typehints > disappear for optional parameters, but it seemed like there was a lot of > s

[PHP-DEV] Re: [PHP-CVS] cvs: php-src /ext/sybase_ct php_sybase_ct.c

2004-05-14 Thread Alex Kiesel
Hi Internals, hi Timm, On Sat, 2004-01-24 at 03:17, Timm Friebe wrote: > @- Fixed bug #22403 "PHP crashes when executing a sql procedure without > @ parameters" (Timm) > @- Fixed memory leak in sybase_set_message_handler() (Timm) > # Fixed bug with large numerics correctly (initial fix i

[PHP-DEV] Type hints resolution?

2004-05-14 Thread Hans Lellelid
Hi, I just wanted to find out what the final resolution was on the typehints discussion for RC3. I know that I (& others) will be sad to see typehints disappear for optional parameters, but it seemed like there was a lot of support for this from others on the list. I didn't get a clear sense

RE: [PHP-DEV] PDO (was: SQLite API deficiency)

2004-05-14 Thread Marc Boeren
Hi, > i'll update the checkout on my server but you will have it through > PECL anyway in a week. I'll wait :-) > > Great. What are the initial backends that will be supported? SQLite, > > MySQL, PGSQL? > > SQLite and Oracle first. We're hoping that the exact two you mentioned > follow very sh