Weird behavior with mislocked: oct-file is unloaded while checking lock state...

[John W. Eaton]

On  3-Sep-2008, Michael Goffioul wrote:

| On Tue, Sep 2, 2008 at 9:13 PM, John W. Eaton <jwe at bevo.che.wisc.edu> wrote:
| > | I'm a little bit confused about this. John, could you give me a hint?
| >
| > Probably there should be a check here to ensure that FUNCTION is not
| > locked, and not clear it if it is locked.
| 
| Shouldn't this be a problem for any oct-file with internal static variables?
| Is such oct-file always supposed to lock itself? In the end, why is the
| oct-file reloaded, as no modification has been made to it?

The function shouldn't be invalidated unless the time stamp changes or
it is no longer visible.  Does the following change fix that problem?
I'm still not sure this is completely the correct thing to do, but I
think it will avoid the problem you are seeing.

Thanks,

jwe


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diffs
Url: https://www-old.cae.wisc.edu/pipermail/octave-maintainers/attachments/20080903/adbb609c/attachment.ksh