Torben Nehmer wrote:
> > Yes. You can re-enable it with --with-old-mod-midgard. Calls to
> > mgd_eval are replaced with eval("?>".mgd_preparse(...
>
> Doesn't that parameter switch to non-MMP Mode? I'm using MMP...
It re-enables some functions that should be obsoleted by MMP.
> "Midgard specific stuff" is what exactly? Does it expect HTML or PHP
> Code?
mgd_preparse does both, replacing mgd_eval (and eval, if you so wish),
mgd_snippet, mgd_include and the &(...); and <[...]> stuff. It expects
the string passed to start as HTML.
> I do not, I depend on a documentation about this. Especially the whole
> Formatter things. Questions like which formatter does Midgard
> expansion, which not, when do I have to use mgd_preparse, how do I do
> eval() constructs with Midgard support. All those things would be
> really nice if there is some place where they are defined.
Yes. They would.
> What I would _wish_ is something like this about the whole formatter
> thing:
>
> - - A function, that works like mgd_eval but does expand Midgard specific
> things withing non-PHP parts of the construct.
Not possible without re-implementing the Zend eval (which is what mgd_eval
previously did). eval works in the scope of the code that calls it. A
function, _any_ function, works in its local scope unless you explicitly
name the variables you want to be globals, and even then it only works
in the global scope, not the calling scope.
> - - A function with which I can parse some HTML with Midgard support.
mgd_preparse?
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
