Most likely, somewhere along the way, one of your files is triggering some
condition which 'unsets' your variable.
That's what it looks like. I can't find anything in the documentation or
on the 'Net that describes such a condition. That's why I originally
posted the question.
Personally, I alwa
James \(IFMS\) wrote:
> I'm struggling to narrow this down, and am chasing my tail to figure
> this out. I apologise for the imprecise nature.
>
> PHP: 4.3.2 (latest RHEL 3 version; php-4.3.2-19.ent.src.rpm)
> OS: Linux kernel 2.4.21-15.0.3.EL
> Distro: RHEL 3, all updates
>
> I have an app that de
As long as you've got something that is consistent and reproducible then
eventually some sense can be made out of it. But if you're saying that
running the same code without changes repeatedly will give random results
then *that* doesn't make sense.
Very true. I wasn't too clear.
Switching aroun
On Monday 10 January 2005 03:34, James (IFMS) wrote:
> I'm currently trying to determine rhyme or reason for the problem, but
> haven't found any pattern.
OK, but ...
> It comes and goes depending on which file
> first calls require_once and the order,
... doesn't this contradict the above?
I'm struggling to narrow this down, and am chasing my tail to figure
this out. I apologise for the imprecise nature.
PHP: 4.3.2 (latest RHEL 3 version; php-4.3.2-19.ent.src.rpm)
OS: Linux kernel 2.4.21-15.0.3.EL
Distro: RHEL 3, all updates
I have an app that defines two global class instances, on
5 matches
Mail list logo
