Re: 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/