Hi
>
> > I use EmbperlObject very much in my own projects and never see
> this problem.
>
> I may be doing something wrong, but I can't see it myself. Now
> this code is
> tested on two different servers with Embperl installed. I use
> Apache 1.3.12 and
> mod_perl 1.24
>
I have tried your page an
>
> Yes, that is correct. but the fact whether or not you actually use this
> variable does not appear to affect the 'bug'.
>
> The problem lies in the fact that the mailserver is expecting a
> "MAIL" command. As long as that one is not send (and it isn't since
> embperl does't even get that far,
The param parameter of Execute is used when you call a whole file (not just
one sub in it). When calling a sub you can directly pass parameters:
call like:
Execute({inputfile => 'test3.imp', import => 1}); # import the sub into
the current namespace (needed only once)
testParams(\@p);
hi,
but everytime I restart apache, Embperl dumps a lot
> of these warnings ...
>
>
> Constant subroutine optRedirectStdout redefined at
> /usr/lib/perl5/5.00503/consta
> nt.pm line 175.
I guess you have PerlFreshRestart on. In this case it's a normal behaviour,
because mod_perl reloads Embperl
> In the following example executing function get_alerting from
> module return
> array with 1 element and its always what must be. But the problem is that
> condition in later code (checkbox only) don't work correct. In the example
> above the result is always not checked input box when $fdat{op}
>
> apache 1.3.12
> Apache-Session-1.51.tar.gz
Current version of Embperl doesn't support APache::Session 1.5x, because
Apache::Session 1.5x is newer them Embperl 1.3b3 and there were many changes
of internal of Apache::Session, which makes it incompatible.
Next release of Embperl will support A
