On Tue, Sep 13, 2005 at 05:21:58AM +0200, Gerald Richter wrote:
> > Porting an apache1 / HTML::Embperl app to apache2 / Embperl,
> > and I'm getting segfaults doing an Embperl::Object::Execute
> > under mod_perl. Simple example:
> >
> > - simple.html:
> >
> > 2 + 2 = [+ 2 + 2 +]
> >
> > - execute.html:
> >
> > [- Embperl::Object::Execute({ inputfile => 'simple.html',
> > appname => 'test' }) -]
>
> Looks like your are calling Embperl::Object from within an Embperl page,
> which doesn't make sense to me (also it should not segfault). What do you
> want to do?
The app is my ewok CMS - http://www.openfusion.com.au/labs/ewok/. I use
Embperl::Object::Execute for 'publishing' static pages to an output
scalar (and thence to a file). In ewok the code lives in a perl module
rather than in the page like the example above; the actual app code looks
like this:
if ($Config->{EMBPERL_VERSION} == 2) {
require Embperl::Object;
my $execute = {
appname => 'ewok',
inputfile => "$fs_dir/$f",
output => \$new,
fdat => $fdat,
object_base => $base,
object_stopdir => $src_fs_dir,
object_addpath => [ split /[;:]/, $addpath ],
syntax => 'EmbperlBlocks',
};
Embperl::Object::Execute($execute);
}
Does that make sense Gerald? The corresponding code works fine using
HTML::EmbperlObject::Execute.
Cheers,
Gavin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
