Torben Nehmer wrote:
> > 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.
>
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))?
> 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.
> All I want is a clear line what to do in the future to avoid Problems
> like I currently have them with eval.
eval is a different matter. It's available if you enable it, but I
cannot realy support changing standard Zend behaviour. I've put it in
for backwards compatibility and I'll keep it in for as long as is
required.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
