PHP_FALIAS()

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello BuildSmart,

If you have the correct includes in place, sure.

marcus

Thanks for the response, OK I think I can manage that with ease, what
I'm contemplating to do is create a mysql_alias extension that
aliases the mysql extension functions to the mysqli equivalents since
a lot of scripts and packages are already dependent on the mysql
extension but it's been deprecated (so I've been informed) and I was
thinking of a simple method to allow the dropping of the mysql
extension in favor of the mysqli extension without having to rewrite
existing scripts and packages.

Since you claims it's possible to alias an external extensions
functions I guess it's just a matter of getting the includes worked
out and what headers need to be loaded in the faking module.

This will probably require a little finessing but shouldn't be too
difficult or complicated.

Actually if you look at zend_API.h which contains ZEND_FALIAS
(PHP_FALIAS /main/php.h) you'll notice that as long as the includes
are done, it's quite trivial to do :)

Good luck,

Saturday, September 8, 2007, 11:36:15 AM, you wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've seen several examples of PHP_FALIAS within a single module, I'm
wondering if it's possible to have one module with aliases
referencing functions in another module?

• -- Dale
  -----BEGIN PGP SIGNATURE-----
  Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFG4m0P0hzWbkf0eKgRAmlXAKChGWEIl+Hz9uOFVFv76qddNH0T5wCeIllB
VsN5vneLwIMBXwBTSEzSbH0=
=fw4n
-----END PGP SIGNATURE-----

Best regards,
Marcus

• -- Dale

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFG5Uc00hzWbkf0eKgRAomHAKCegTASJWoqwHi+szmDwiXU82wVdQCgqzBT
uf2junm3kDfwnOZzDTnCKOI=
=+07f
-----END PGP SIGNATURE-----

--

--
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18

Hi,

On Monday 10 September 2007 03:31:32 pm BuildSmart wrote:

Thanks for the response, OK I think I can manage that with ease, what
I'm contemplating to do is create a mysql_alias extension that
aliases the mysql extension functions to the mysqli equivalents since
a lot of scripts and packages are already dependent on the mysql
extension but it's been deprecated (so I've been informed) and I was
thinking of a simple method to allow the dropping of the mysql
extension in favor of the mysqli extension without having to rewrite
existing scripts and packages.

I, personally, don't think it's such a good idea to replace the dependency of
the mysql extension with an dependency on two extensions, mysql_alias+mysqli,
and also you should keep in mind that ext/mysql and ext/mysqli might work a
bit different in a few minor places.

For going from ext/mysql to ext/mysqli the MySQL guys have some conversion
script somewhere on their site afaik.

And a last thought: If you need a wrapper wrapping ext/mysql API over mysqli
I'd do it in PHP since distributing PHP code is way simpler than distributing
some extension and the performance lost can be ignored since most time is
still lost while doing communication with the database server. (the few
exceptions usually can do other optimizations giving better results or simply
use no wrapper)

johannes

Johannes Schlüter
http://schlueters.de

BuildSmart wrote:

Thanks for the response, OK I think I can manage that with ease, what
I'm contemplating to do is create a mysql_alias extension that aliases
the mysql extension functions to the mysqli equivalents

uh .... PHP_FALIAS() would only work for functions having
exactly the same parameter signature ... so it would only
work with a very minor subset of the mysql/mysqli functions
(if at all). For a lot of functions the signature changed
so that the database handle is now the first parmeter
instead of the last, and even for those that look similar
you have to take into account that mysqli relies on objects
(even for the procedural style functions) where ext/mysql
is all about resources, not objects.

There is also the concept of the default connection
in ext/mysql that does not exist in ext/mysqli at all
so that can't be emulated by just aliasing functions
either ...

While a ext/mysql -> ext/mysqli compatibility wrapper
might make sense it is way more effort to create one,
and if you really want to go that way i'd recommend
that you do a proof-of-concept implementation using
PHP code first before starting the effort to wrap
it up in a C extension.

That aside i don't think that it would make much sense
to create such a wrapper, ext/mysql being deprecated
says that we won't add any new features to it. There
are no plans to remove it though and any serious security
issues or possible incompatibilities with newer libmysqlclient
versions will still be fixed.

--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:
http://www.mysql.com/products/enterprise/whats_new.html

Hauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140