Re: Use fsock.c from my module
| From: | Ignacio Vazquez-Abrams | Date: | Fri, 01 Dec 2000 17:03:15 +0000 |
| Subject: | Re: Use fsock.c from my module | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-39797@lists.php.net to get a copy of this message | ||
On Fri, 1 Dec 2000, Sam Liddicott wrote:
> In order to keep my network interface portable I thought it better to write
> using fsock.c and require that sockets be enabled for php.
>
> Is this advisable?
>
> In my config.m4 how do I check that --enable-sockets is active?
>
> In my config.m4 how do I cause to be defined somewhere one of the PATHS
> calculated by config.m4 - in order that my C module knows the compile time
> paths as defaults for other things.
>
>
> Thanks
>
> Sam
>
This makes your code portable across operating systems, but not across PHP
installations. IIRC, there have been plenty of cases where sockets don't
compile correctly but aren't needed anyway; your extension would be completely
unusable in these cases. AFAIK the right way to do portability, unfortunately,
is to go through all the #ifdef loops.
--
Ignacio Vazquez-Abrams <ignacio@openservices.net>