-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi.
- --On 28.03.2002 12:11:08 +0100 Emiliano wrote:
>> But previously, mgd_eval worked like eval, which expects to start in
>> PHP mode... If we keep this function, we should keep the syntax.
>
> Did it? I agree that functionality should remain unchanged... I can't
> remember exactly. The preparser was largely based on the parser that
> used to be in midgard-php4. It's easy to change (remove a few chars in
> the preparser).
>
> The parser translates mgd_eval(whatnot) into
> eval("?>".mgd_preparse(whatnot)) which suggests to me that mgd_eval
> used to expect to start in HTML mode. mgd_preparse does expect to
> start in html mode, that I do know. But what you're saying is that
> mgd_eval(whatnot) should map to eval(mgd_preparse("?>".whatnot))?
As far as I remeber, mgd_eval worked with the same semantics as the
classic eval. So the latter beavoir sould be used. Anything else would
be irritating anyhow, since many will associate mgd_eval and eval
together.
>> 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.
>
> But it is always available. Just not as a function.
Oh... Well, than it seems that I didn't understand you correctly
earlier *lookinginnocent* Sorry...
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
iD8DBQE8ovx2JPh4Kn6d5FYRAn7BAKCAyNmYAEW+THyTiBek88olqx3WGACfTGfh
XyOdKMq8M7nnx2sGX//NdOI=
=+MYq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
