@param is a special variable and you use it in an unsupported way (see my other
mail).
Any other global should be cleaned up at the end of the request
Gerald
> -Original Message-
> From: Michael Stevens [mailto:[email protected]]
> Sent: Wednesday, July 21, 2010 12:46 PM
> To
My actual problem is occuring under Apache, and what I'm expecting is
for things to be cleaned up between requests, which isn't happening.
But even this small test case is not the way I'd expect things to behave.
On 20/07/10 22:20, Ed Grimm wrote:
Note that, under Apache, the cleanup code happ
Thanks, I will apply your patch in the next release
gerald
> -Original Message-
> From: Michael Stevens [mailto:[email protected]]
> Sent: Tuesday, July 20, 2010 3:57 PM
> To: [email protected]
> Subject: Few minor spelling nits
>
> Hi.
>
> Was trying to work out how exe
Hi,
I ran accross this issue (with the path parameter) some days before on my own.
I will fix it, so a error message is generated instead of a seg fault
Gerald
> -Original Message-
> From: Michael Stevens [mailto:[email protected]]
> Sent: Tuesday, July 20, 2010 4:07 PM
> To:
Hi Michael,
@param is only intented to be used to pass parameters to Execute. Setting it
directly might work or might not…
If you want to share data inside a request use
$epreq -> {test} = 1 ;
The hash of $epreq is not used by Embperl itself, so you are free to use it and
it exis
Hi,
Am 21.07.2010 um 11:05 schrieb Michael Smith:
> My problem is slightly different - though possibly a manifestation of the
> same thing. I find that param isn't cleaned up between requests.
>
> I have two epl files:
>
> set.epl:
> [- $param[0]->{'test'} = 1 -]
>
> get.epl
> [+ Dumper(@par
My problem is slightly different - though possibly a manifestation of the
same thing. I find that param isn't cleaned up between requests.
I have two epl files:
set.epl:
[- $param[0]->{'test'} = 1 -]
get.epl
[+ Dumper(@param) +]
I find that the data from set.epl turns up when I make a subseque
