Not to beat a dead horse, but I'm glad someone else noticed this. I
almost went back to bed, thinking the whole world had gone mad. :)
On Mon, 25 Jun 2001, Jani Taskinen wrote the following to Zeev Suraski :
tagged as experimental makes it easier for us to change the API to a
PHP-like API,
Maybe we should wait with this whole API change until a new sub-version?
4.1? Or keep the old functionality right now and just add the new
functions? We can deprecate the old ones in 4.1.
Andi
At 03:03 PM 6/24/2001 +0200, Jani Taskinen wrote:
Since everybody seems to be using some stupid
On 24 Jun 2001 17:43:02 +0200, [EMAIL PROTECTED] wrote:
The documentation has just been updated, stating that the sockets-module is
still experimental.
As has any module having an EXPERIMENTAL file in it's directory.
Because of the experimental status, I don't think phpdev should worry too
jani,
At 20:21 24.06.2001 +0200, Jani Taskinen wrote:
What new functionality? Why the hell should the API change?
Only the function names should have been changed, not break
the whole extension!
the issue that made the extension break was the step from resources to
longs for the socket fd's,
Because of the experimental status, I don't think phpdev should worry
too
much about the
incompatibility, it's the user's own reponsibility to use an
experimental
module.
Taking a look at the changes to the sockets extension, some break things
on a Linux system, some don't work at all,
At 20:58 24.06.2001 +0200, Daniel Beulshausen wrote:
jani,
At 20:21 24.06.2001 +0200, Jani Taskinen wrote:
What new functionality? Why the hell should the API change?
Only the function names should have been changed, not break
the whole extension!
the issue that made the extension break was
On Sun, 24 Jun 2001, Daniel Beulshausen wrote:
the issue that made the extension break was the step from resources to
longs for the socket fd's, this was necessary as win32 socket fd's are
different from bsd style socket fd's.
So this is broken now only on *nix? Nice.
Previously it worked only
At 21:10 24.06.2001 +0200, Jani Taskinen wrote:
On Sun, 24 Jun 2001, Daniel Beulshausen wrote:
the issue that made the extension break was the step from resources to
longs for the socket fd's, this was necessary as win32 socket fd's are
different from bsd style socket fd's.
So this is broken
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jani Taskinen
Sent: Sunday, June 24, 2001 9:11 PM
To: Daniel Beulshausen
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] About ext/sockets/
On Sun, 24 Jun 2001, Daniel Beulshausen wrote
On 24 Jun 2001 21:40:19 +0200, Lukas Beeler wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jani Taskinen
Sent: Sunday, June 24, 2001 9:11 PM
To: Daniel Beulshausen
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] About ext/sockets
[don't break the API!]
i'd vote not for changing the api back, rather than
updating/extending the
yet available (tiny) sockets documentation.
I vote we get the old api back. I don't care if it doesn't
support win32.
1) IMHO the new API is better (the 'write' function is really a name
-Original Message-
From: sterling hughes [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 24, 2001 9:49 PM
To: Lukas Beeler
Cc: [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] About ext/sockets/
On 24 Jun 2001 21:40:19 +0200, Lukas Beeler wrote:
-Original Message
Jeroen,
For lower-scale and home-use you can argue it is easier
than *nix. So when possible, you should try to support windows.
[..]
[looked like C, was easier for ppl with C-background]
I don't think you should target php at C-ppl.
PHP has been since its inception strongly
At 22:10 24/6/2001, Jani Taskinen wrote:
So this is broken now only on *nix? Nice.
Previously it worked only on unices, now it works only on win32?
What an improvement.
Let's keep cynicism off this list, please...
About the socket extension - this was discussed, and agreed upon that the
way it
Sascha,
PHP is an established language on its own now, with failure semantics of
its own. Failure in PHP is noted by false and resource (i.e. anything
which is not a language primitive or composite type) are contained in
IS_RESOURCE handles. The original socket implementation was wrong in
]]
Sent: June 24, 2001 2:19 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] About ext/sockets/
Jeroen,
For lower-scale and home-use you can argue it is easier
than *nix. So when possible, you should try to support windows.
[..]
[looked like C, was easier for ppl with C
On Mon, 25 Jun 2001, Zeev Suraski wrote:
At 22:10 24/6/2001, Jani Taskinen wrote:
So this is broken now only on *nix? Nice.
Previously it worked only on unices, now it works only on win32?
What an improvement.
Let's keep cynicism off this list, please...
:-p
About the socket extension - this
, and I was very happy to see sockets making it to windows.
-Brian Tanner
-Original Message-
From: Sascha Schumann [mailto:[EMAIL PROTECTED]]
Sent: June 24, 2001 2:19 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] About ext/sockets/
Jeroen,
For lower
At 03:23 25/6/2001, Brian Tanner wrote:
Considering a very low % of PHP programmers have extensive C socket
experience, I wouldn't worry too much about making it inconvenient. You
guys are just a little biased (IMHO), because you are all talented,
experienced, C programmers.
Not all of us are
At 08:21 PM 6/24/2001 +0200, Jani Taskinen wrote:
What new functionality? Why the hell should the API change?
Only the function names should have been changed, not break
the whole extension!
It's a rewrite which is more in the PHP spirit. i.e. return true/false and
not -1/0 and stuff like that
20 matches
Mail list logo
