Re: _EXTRA inheritance crashing IDL [message #34966 is a reply to message #34870] |
Tue, 29 April 2003 15:05  |
Mark Hadfield
Messages: 783 Registered: May 1995
|
Senior Member |
|
|
"M A lewis" <mal11@po.cwru.edu> wrote in message
news:c8765746.0304291150.534f349b@posting.google.com...
> In IDL 5.6, it appears that the fatal _REF_EXTRA bug was fixed, but I
> am wondering if I have found another bug. Try these 2 simple
> procedures:
> PRO test1, _REF_EXTRA=ex
> test2, _EXTRA=ex
> ;test2, _EXTRA=['BLAH1','BLAH2']
> END
>
> PRO test2, BLAH1 = blah1, BLAH2 = blah2
> PRINT, "test2 called"
> IF KEYWORD_SET(blah1) THEN PRINT, "Blah1 passed!"
> IF KEYWORD_SET(blah2) THEN PRINT, "Blah2 passed!"
> END
>
> Notice the first way of calling test2 in test1. This has all the
> expected behavior. The second manner that is commented out should work
> the same. But try passing just one keyword.
> test1, BLAH2=2.0
> For me with IDL 5.6 under WinXP Pro, this crashes IDLDE with an
> invalid memory read. If someone else can confirm that this is a bug,
> I will report it...
I get it too (IDL 5.6 on Win 2000). It's not 100% consistent. In playing
around with your example I managed to crash IDLDE several times in the way
you describe, but in my current session everything seems to be working OK.
(I think it's something to do with the order in which I tried things out.)
And on one occasion I got an internal memory error rather than a crash (I
didn't note it down at the time, but it was something about an invalid
IDL_kwvariable)
By the way, why are you using the _EXTRA=['BLAH1','BLAH2'] syntax? I haven't
found it very useful.
--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|