I managed to delete all the emails in this thread, so apologies for
screwing up the threading thing...
Seems like SourceForge might be a good place to host this, under a
suitable project name, with some basic understandings of "fair play"
E.g.:
Add new directory names that make sense, or perhaps
On Fri, December 8, 2006 10:03 am, Ilia Alshanetsky wrote:
> COM:
> Un-maintained at this time and has a fairly serious number of bugs
> (26 by latest count, many of which are crashes)
> Only usable to Win32 users, which I think we all admit are a
> minority and can always download read
Ilia Alshanetsky wrote:
> Well, it does not consume any resources simply because no one is
> maintaining it ;-). How really different things would be if it were in
> pecl? I mean afaik COM is not enabled by default on win32, so you still
> need to enable it manually. So, the only extra step for pe
> On 12/08/2006 07:03 PM, Ilia Alshanetsky wrote:
>
> > COM:
-1
COM should have more attention and I can try to find some of that.
> > mhash:
+1
> > sockets:
+1 when everything can be handled by streams
- Frank
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
Hi,
On Fri, 2006-12-08 at 13:17 -0500, Ilia Alshanetsky wrote:
> On 8-Dec-06, at 1:01 PM, Stanislav Malyshev wrote:
>
> >> COM:
+1, easy to install from pecl.
> >> mhash:
> >> sockets:
> >> Un-maintained.
> A good point for 5.2, but given that there is no one to support users
> using t
At 21:51 08/12/2006, Derick Rethans wrote:
On Fri, 8 Dec 2006, Ilia Alshanetsky wrote:
> This is an exploratory e-mail, so don't panic just yet :-). I am
thinking of
> moving the COM, mhash and socket extensions to PECL in 5.2 and 6.0 releases
> and was hoping to hear for & against arguments.
Hello,
On 12/8/06, Stefan Esser <[EMAIL PROTECTED]> wrote:
>> >> c) Support Cookies correctly...
>> Very simple: In some earlier version php_register_variable_ex was
>> changed to handle cookies different from other variables: Cookies with
>> the same name will get dropped after the first is re
>> >> c) Support Cookies correctly...
>> Very simple: In some earlier version php_register_variable_ex was
>> changed to handle cookies different from other variables: Cookies with
>> the same name will get dropped after the first is registered.
>> In ext filter the raw variables still have this b
On Fri, 8 Dec 2006, Ilia Alshanetsky wrote:
> This is an exploratory e-mail, so don't panic just yet :-). I am thinking of
> moving the COM, mhash and socket extensions to PECL in 5.2 and 6.0 releases
> and was hoping to hear for & against arguments.
> The reason for the making this move are as f
Hello,
On 12/8/06, Stefan Esser <[EMAIL PROTECTED]> wrote:
> This is where you are incorrect, take a look at
> php_register_variable_safe() line #51. The reason we don't apply magic
> quotes for PARSE_STRING (retval == 1) is because the return value of
> the function in this instance is 1, whic
Hello,
On 12/8/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
This is an exploratory e-mail, so don't panic just yet :-). I am
thinking of moving the COM, mhash and socket extensions to PECL in
5.2 and 6.0 releases and was hoping to hear for & against arguments.
The reason for the making this
I'm OK with all except for COM.
I've actually used the COM extension quite a bit internally here for
reporting and creating Excel files (see one of my blog postings from about a
year ago). I think for those who are on Windows it's a really handy
extension. Last time I checked it was also always ena
Well, it does not consume any resources simply because no one is
maintaining it ;-). How really different things would be if it were in
I meant runtime resources, not developer resources. Like memory, CPU, etc :)
pecl? I mean afaik COM is not enabled by default on win32, so you still
need to
On 8-Dec-06, at 1:01 PM, Stanislav Malyshev wrote:
COM:
Un-maintained at this time and has a fairly serious number of
bugs (26 by latest count, many of which are crashes)
I don't think COM should be moved out. Right, it's windows only -
but if you are on windows, COM extension is most
COM:
Un-maintained at this time and has a fairly serious number of bugs
(26 by latest count, many of which are crashes)
I don't think COM should be moved out. Right, it's windows only - but if
you are on windows, COM extension is most useful (I used it a number of
times and it's really am
On 12/08/2006 07:03 PM, Ilia Alshanetsky wrote:
COM:
mhash:
sockets:
+1 +1 +1
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky wrote:
> COM:
+1
> mhash:
+1
> sockets:
+1
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visi
This is an exploratory e-mail, so don't panic just yet :-). I am
thinking of moving the COM, mhash and socket extensions to PECL in
5.2 and 6.0 releases and was hoping to hear for & against arguments.
The reason for the making this move are as follows:
COM:
Un-maintained at this time and ha
18 matches
Mail list logo
