Hi,
thanks for the suggestion. I wrote a TestFor package, pretty straight according to the documentation, as seen below. The problem persists, and besides TIEARRAY and DESTROY once and many times FETCHSIZE, there is no method called on @e.
To clarify:
| [reply]
[d/l]
[select] |
The only other suggestion I have (which at least won't involve so much work!), is to see if you get the same problem if the array is a global: our @e.
Beyond that, it sounds like you just have a broken build. Rebuild it, or if its a vendor build grab an ealier one and report the problem to whomever built it.
Even if you tracked down what caused it, what would you do about it?
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply]
[d/l] |
Yes, I do, no change with 'our @e'.
I'm going now for steamroller tactics ... I reinstall all the distribution packages in order to avoid corrupted data.
What I would do about it? Well, that would strongly depend on the cause, once I knew it ... :)
| [reply] |