Hi,
That's the reason why I started writing an ext for PHP that would
implement epoll() on linux, and stuff-with-ws2 on Win32.
However I don't mind making this a patch to the stream ext.
Basically I get the following functions:
consts:
STREAM_POLL_IN (read)
STREAM_POLL_OUT (write)
STREAM_POLL_
Robin Burchell wrote:
> On Thu, Feb 19, 2009 at 10:24 PM, Andrei Zmievski
> wrote:
>> Can someone explain why ext/sockets and also stream socket functions care
>> about FD_SETSIZE?
>
> They care, because they use the select(2) syscall, which cares about
> FD_SETSIZE.
>
select(2) itself can ha
That's because struct fd_set, which is manipulated by FD_SET, is a
struct that contains a fixed-size array.
Moriyoshi
Andrei Zmievski wrote:
> Can someone explain why ext/sockets and also stream socket functions
> care about FD_SETSIZE?
>
> # define PHP_SAFE_FD_SET(fd, set) do { if (fd < FD_SE
On Thu, Feb 19, 2009 at 10:24 PM, Andrei Zmievski wrote:
> Can someone explain why ext/sockets and also stream socket functions care
> about FD_SETSIZE?
They care, because they use the select(2) syscall, which cares about FD_SETSIZE.
--
PHP Internals - PHP Runtime Development Mailing List
To un
Can someone explain why ext/sockets and also stream socket functions care about
FD_SETSIZE?
# define PHP_SAFE_FD_SET(fd, set) do { if (fd < FD_SETSIZE) FD_SET(fd, set);
} while(0)
On Linux, it's not a hard limitation imposed by the kernel. It's configurable
via sysctl.
-Andrei
--
PHP Inte
The third and final release candidate of 5.2.9 was just released for
testing and can be downloaded here:
http://downloads.php.net/ilia/php-5.2.9RC3.tar.bz2 (md5sum:
11dac673bc41fe607ddae680f4ae10ea)
http://windows.php.net/downloads/qa/php-5.2.9RC3-Win32-VC6-x86.zip
(sha1: 5150afad0bc1760c0
That's a good point we need to make sure that main.c INI values match
those of the production INI file. There are A LOT of installs that
operate without an INI file.
I'd say it's usually ini-dist that matches the main.c value... but the issue
in this case is that ini-recommended (which is gene
That's a good point we need to make sure that main.c INI values match
those of the production INI file. There are A LOT of installs that
operate without an INI file.
On 19-Feb-09, at 12:44 PM, Steph Fox wrote:
allow_call_time_pass_reference = Off (Issue Warnings)
Eric Lee Stewart
+1
Sw
allow_call_time_pass_reference = Off (Issue Warnings)
Eric Lee Stewart
+1
Switching it off by default in ini-dist and main.c would be good too!
http://wiki.php.net/rfc/calltimebyref
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/uns
Eric Stewart wrote:
> We seem to have a split opinion on what the production INI value for
> allow_call_time_pass_reference should be.
>
> As I understand it, this does not enable or disable the ability to pass
> references at call time. It only enables or disables PHP's warnings about
> this beha
Eric Stewart a écrit :
allow_call_time_pass_reference = Off (Issue Warnings)
Hello,
+1 too.
Olivier
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi.
On 19.02.2009 6:34 Uhr, Eric Stewart wrote:
allow_call_time_pass_reference = Off (Issue Warnings)
+1
Karsten
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
did you guys see the other patch i posted yesterday? i re-read Johannes'
first reply yesterday and saw the bit about a second api for a
zend_call_method with a variable number of parameters. so a made a new
function then re-implemented zend_call_method based on that. heres the
patch (easier to re
>
> allow_call_time_pass_reference = Off (Issue Warnings)
>
+1
Elizabeth Smith
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 19-Feb-09, at 12:34 AM, Eric Stewart wrote:
allow_call_time_pass_reference = Off (Issue Warnings)
+1
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sat, 2009-02-14 at 23:06 +, Nuno Lopes wrote:
> Currently PHP's benchmarks are very poor. The PHP interpreter is only timed
> against bench.php. Sadly, this doesn't make use of the majority of PHP's
IS that something where some GSoC student might help? If yes, please add
it to http://wiki.
2009/2/19 Eric Stewart
>
> allow_call_time_pass_reference = Off (Issue Warnings)
>
>
+1
--
Mikko Koppanen
hi,
On Thu, Feb 19, 2009 at 11:57 AM, Johannes Schlüter wrote:
> ps. I'm aware of the fact that we added some specific APIs in special
> cases in bug fix releases before, but there's a difference between
> adding APIs and breaking the ABI of existing, used, stuff.
Exactly. To summarize:
x.y.z
On Thu, 2009-02-19 at 00:14 +0100, Marcus Boerger wrote:
> Stuff like this can imo always be added and whether you do
> #if PHP_VERSION_ID >= 50300
> or
> #if PHP_VERSION_ID >= 50301
> imo doesn't matter much.
It does.
Up till now we always tried to keep binary compatibility for "bug fix"
release
hi Eric,
On Thu, Feb 19, 2009 at 6:34 AM, Eric Stewart wrote:
> allow_call_time_pass_reference = Off (Issue Warnings)
+1
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
20 matches
Mail list logo
