Date: 12/01/00
- Next message: akilov <email protected>: "[PHP-DEV] PHP 4.0 Bug #6381 Updated: Servlet failures"
- Previous message: Sam Liddicott: "RE: [PHP-DEV] Use fsock.c from my module"
- In reply to: Sam Liddicott: "RE: [PHP-DEV] Use fsock.c from my module"
- Next in thread: chrisv <email protected>: "Re: [PHP-DEV] Use fsock.c from my module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 1 Dec 2000, Sam Liddicott wrote:
> I see what you are saying.
>
> Surely all the ifdef loops have been hacked into fsock.c
> If fsock.c won't compile, then my code won't because it has to do what
> fsock.c does.
> Or, whatever fixes would need making to my code in order to compile it could
> be done to fsock to fix that?
>
> Or maybe there's lots of extra stuff in fsock I won't need?
>
> I could rip-off the whole of fsock.c and take out the bits I don't need?
>
> Which would you do?
>
> Thanks for your sage advice here.
>
> Sam
>
The best policy is probably to pick and choose through existing code, although
forcing fsock.c into the compile/link without actually requiring sockets might
work just as well.
-- Ignacio Vazquez-Abrams <ignacio <email protected>>-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: akilov <email protected>: "[PHP-DEV] PHP 4.0 Bug #6381 Updated: Servlet failures"
- Previous message: Sam Liddicott: "RE: [PHP-DEV] Use fsock.c from my module"
- In reply to: Sam Liddicott: "RE: [PHP-DEV] Use fsock.c from my module"
- Next in thread: chrisv <email protected>: "Re: [PHP-DEV] Use fsock.c from my module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

