Jason T. Greene [EMAIL PROTECTED] writes:
The biggest thing I would like to have complete *by 4.3* is good solid
docs on this extension (There is some already done). I am planning on
working on this, and I have had one volunteer to help out.
Where are the current docs? I'd like to have a
On Thu, Sep 12, 2002 at 10:41:47AM -0700, Brian Lalor wrote :
Where are the current docs?
[...]
php.net/sockets
--
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
- It's not a fug, it's a beature. -
--
PHP Development Mailing List http://www.php.net/
To
Markus Fischer [EMAIL PROTECTED] writes:
On Thu, Sep 12, 2002 at 10:41:47AM -0700, Brian Lalor wrote :
Where are the current docs?
[...]
php.net/sockets
By which you mean the source? I asked if there was documentation outside of
the source files.
--
Brian Lalor
[EMAIL PROTECTED]
On Thu, Sep 12, 2002 at 10:54:14AM -0700, Brian Lalor wrote:
On Thu, Sep 12, 2002 at 10:41:47AM -0700, Brian Lalor wrote :
Where are the current docs?
[...]
php.net/sockets
By which you mean the source? I asked if there was documentation outside of
the source files.
Yes,
On 12 Sep 2002, Brian Lalor wrote:
Jon Parise [EMAIL PROTECTED] writes:
By which you mean the source? I asked if there was documentation outside of
the source files.
Yes, the documentation is at http://www.php.net/sockets (which
redirects to the manual entry).
Thanks for
Jon Parise [EMAIL PROTECTED] writes:
On Thu, Sep 12, 2002 at 10:54:14AM -0700, Brian Lalor wrote:
On Thu, Sep 12, 2002 at 10:41:47AM -0700, Brian Lalor wrote :
Where are the current docs?
[...]
php.net/sockets
By which you mean the source? I asked if there was
On Thu, Sep 12, 2002 at 01:13:03PM -0700, Brian Lalor wrote :
Jon Parise [EMAIL PROTECTED] writes:
On Thu, Sep 12, 2002 at 10:54:14AM -0700, Brian Lalor wrote:
On Thu, Sep 12, 2002 at 10:41:47AM -0700, Brian Lalor wrote :
Where are the current docs?
[...]
Jason Greene [EMAIL PROTECTED] writes:
This extension does not belongs in PECL. It is fully platform
compatible, all other languages offer this functionality, it is actively
maintained (by me), and it will be marked stable by version 4.3
Jason, can you help me understand what needs to be
What I was saying in my earlier email much longer drawn out email was,
that the API changes have been really final since version 4.2.0. The
only reason I would change it, would be if someone demonstrated a
problem with the interface, which no one has for 4.2.0 - 4.2.3 versions.
The only API
