RE: [PHP-DEV] Symbol clash between Recode and MySQL extensions

From: Date: Sun, 13 Feb 2005 07:20:20 +0000
Subject: RE: [PHP-DEV] Symbol clash between Recode and MySQL extensions
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-14896@lists.php.net to get a copy of this message
> -----Original Message----- > From: Jani Taskinen [mailto:sniper@iki.fi] > Sent: Sunday, 13 February 2005 5:25 PM > To: php@newmillennium.net.au > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Symbol clash between Recode and MySQL > extensions > > > > Also documented in the manual: > > http://www.php.net/recode Got it, thanks. > Just blame recode and mysql. They both should namespace > protect their > functions. :) Agreed. However, if a workaround is available, it would benefit everyone to implement it. I was thinking that rather than linking against the recode library (and implicitly importing all symbols within it), we could instead dlopen() it, and use dlsym() to import only symbols we want. Looking at the recode extension, theres only a handful of entrypoints that need to be imported, so it should be a relatively easy task for someone familiar with the PHP API. -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au

« previous php.internals (#14896) next »