-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
- --On 28.03.2002 11:09:36 +0100 Emiliano wrote: >> Am I correct in the assumption, that mgd_eval expects to start in >> PHP mode? > > Just the opposite; it expects to start in HTML mode, which is why > you'll see nearly all the code start with "<?php", which puts you in > PHP mode. But previously, mgd_eval worked like eval, which expects to start in PHP mode... If we keep this function, we should keep the syntax. >> If the parser replaces it with mgd_preparse construct, I'd suggest >> putting this Macro back into the active function tree without having >> to enable it explicity. This would keep us a point where we can hook >> in the Midgard specific eval encaspulation. If we need changes here >> in the future, we can just change this macro, and do not procduce >> problems like the current one. > > I don't understand. What I mean is: If we encourage people to use mgd_eval instead of mgd_preparse, mgd_eval should be available always, not only if you activate it with --with-old-mod-midgard. All I want is a clear line what to do in the future to avoid Problems like I currently have them with eval. 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: Weitere Infos: siehe http://www.gnupg.org iD8DBQE8ovJ4JPh4Kn6d5FYRAl0jAJ4xTDrCbAuZDE/7M5Hmdiktwd4pcACgxAyu jNpL3sl1EfNSfjz5EYW8Pxs= =TneM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
