Re: Re: [PHP-DEV] mcrypt 2.4
| From: | PHP development @echospace | Date: | Wed, 19 Jul 2000 22:12:29 +0000 |
| Subject: | Re: Re: [PHP-DEV] mcrypt 2.4 | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-25158@lists.php.net to get a copy of this message | ||
Can we do something like this?:
say, we determine if mcrypt2 is installed and have MCRYPT2 defined if this is the case. Now,
#ifdef MCRYPT2
<here goes code for the new API>
#else
<here goes code for the old API>
#endif
Or is this the BAD THING (tm)?
I realize that this is a somewhat ugly approach, but besides ugliness I do not see any drawbacks
compared to creating a brand new module.
I assume that although API has changed, we can still keep all the functions used in mcrypt module
before with the same syntax, and add new ones on top of that, if necessary. The only thing that
changes is the way we use mcrypt library from our module.
Vlad
----- Original Message -----<BR>From: Derick Rethans
To: Sascha Schumann <SASCHA@SCHUMANN.CX>
Sent: Wed, 19 Jul 2000 22:48:15 +0200
Subject: Re: [PHP-DEV] mcrypt 2.4
Sascha Schumann wrote:
> On Wed, 19 Jul 2000, Derick Rethans wrote:
>
> > Hello,
> >
> > nobody gave a reaction, so I asume I've something to do this evening :-)
>
> We are glad to consider integration of user-provided patches. :)
>
> I actually have planned rewriting the module from scratch, but
> there is this issue called available time. ;(
The API has totaly changed, so the module had to be rewrited after all (As I
see). Question is, if the mcrypt extension as it exists now, must be extended
with the new API (almost all of the functions have to be changed as I see), or
create a new extension for it. Preferable the first option of course.
ANother posiblility is to retain all functions as they are now (for mcrypt
2.2), and add new mcrypt2_* functions for the new API (mcrypt 2.4).
Did you already have some design in mind, or didn't you?
Derick Rethans
JDI Media Solutions
H.v.Tussenbroekstraat 1
6952 BL Dieren
The Netherlands
e-mail: d.rethans@jdimedia.nl
http://www.jdimedia.nl/
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
For additional commands, e-mail: php-dev-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net
________________________________________
Finally! Real applications on the web!
Free email, contacts, and file storage.
http://www.echospace.com