-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
- --On Mittwoch, M�rz 20, 2002 19:11:03 +0100 Emiliano <[EMAIL PROTECTED]> wrote: >> > > If you change the eval to mgd_eval, everything works out fine. >> > >> > BTW, I updated Asgard for this problem early January. >> >> ... meaning I should get a Asgard-<something>xml.gz from cvs and >> import it to 'unbreak' Asgard??? > > If you're going to use MMP, yes. 1.4.1 and 1.4.2 augmented the > behaviour of standard eval by replacing it with mgd_eval inline. The > MMP preparser doesn't. I changed calls of eval(...) to > eval(mgd_preparse(...)) in Asgard to deal with that. If absolutely > required I could easily, but reluctantly, put back the inline > replacement of eval. mgd_eval will remain of course. As I've said, I know of several applications, that depend on the eval construct working the old way. Suggestion: Is it possible, to optionally enable the old behavoir? It would give (at least) us a lot of time to port the older applications. Create a new chapter in the docs where you explicitly talk about the different eval-things (what's mgd_preparse about, vs the mgd_eval?). Mention explicitly, that the use of eval for Midgard constructs is deprecated and that it is _not_ enabled by default and only there for the sake of compatibility. For me it would even be enough, if you could do that "remapping" within php as a runtime directive, if this is possible. Live long and prosper! Torben Nehmer - -- Torben Nehmer, Munich, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key ID on wwwkeys.(de.)pgp.net: 0x7E9DE456 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8mOjVJPh4Kn6d5FYRAli2AKDe+eSKfL5iUjTqNfQyIhwrzX92FgCeNuoU q9uefiTveIJbRYWjAVCD9tE= =5AMG -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
