comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Hard crash

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Hard crash [message #90139 is a reply to message #90137]

Fri, 30 January 2015 15:39

Heinz Stege
Messages: 189
Registered: January 2003

Senior Member

On Fri, 30 Jan 2015 13:25:45 -0800 (PST), fawltylanguage@gmail.com
wrote:

> I can confirm that it was there two hours ago. Now it is here:
>
> http://www.exelisvis.com/Company/PressRoom/Blogs/TabId/836/A rtMID/2928/ArticleID/14277/Problems-Assigning-LIST-HASH-etc- to-Class-or-Structure-Tags.aspx
>
> Read quickly before it changes its address again :-)
>
Thank you Lajos. The second link is working for me to. :-)

However I wonder, if the most important point isn't that in the
comment: "BUT you should use the SKIP keyword to RESOLVE_ALL before
creating your SAVE file to ensure the "hash.sav" file is NOT included
in your build."

I don't use lists and hashes frequently, but does it really make a
change to use OBJ_NEW() instead of LIST() in the class definition?
Don't misunderstand me, it is always a good idea to be clearly in
coding. So it may be more readable to use OBJ_NEW().

But what is the difference? When I define two structures
s1={a:list()}
s2={a:obj_new()}
IDL's help command
help,s1,s2,/str
prints:
** Structure <1606fea8>, 1 tags, length=4, data length=4, refs=1:
A OBJREF <ObjHeapVar1(LIST)>
** Structure <11587c78>, 1 tags, length=4, data length=4, refs=1:
A OBJREF <NullObject>
There are object references in both structures s1 and s2. The first
one s1 is already allocated in the heap, the second one s2 is a null
object. But somewhere in the code I have to make it a list:
s2.a=list()
And then the help command says, that s2 is equal s1:
** Structure <11587c78>, 1 tags, length=4, data length=4, refs=1:
A OBJREF <ObjHeapVar2(LIST)>
Is there something wrong in my understanding?

Cheers, Heinz

Report message to a moderator

[Message index]

		Hard crash By: Helder Marchetto on Thu, 18 December 2014 07:20
		Re: Hard crash By: chris_torrence@NOSPAM on Thu, 18 December 2014 08:08
		Re: Hard crash By: Matt Haffner on Fri, 19 December 2014 13:34
		Re: Hard crash By: Jim Pendleton on Fri, 19 December 2014 20:52
		Re: Hard crash By: chris_torrence@NOSPAM on Sat, 20 December 2014 14:34
		Re: Hard crash By: Matt Haffner on Thu, 08 January 2015 13:45
		Re: Hard crash By: chris_torrence@NOSPAM on Thu, 08 January 2015 14:34
		Re: Hard crash By: Jim Pendleton on Thu, 08 January 2015 18:17
		Re: Hard crash By: Matt Haffner on Fri, 09 January 2015 11:31
		Re: Hard crash By: Jim Pendleton on Fri, 09 January 2015 17:13
		Re: Hard crash By: David Fanning on Fri, 30 January 2015 09:25
		Re: Hard crash By: Heinz Stege on Fri, 30 January 2015 13:15
		Re: Hard crash By: Lajos Foldy on Fri, 30 January 2015 13:25
		Re: Hard crash By: Heinz Stege on Fri, 30 January 2015 15:39
		Re: Hard crash By: Jim Pendleton on Fri, 30 January 2015 17:24
		Re: Hard crash By: markb77 on Mon, 02 February 2015 07:09
		Re: Hard crash By: Heinz Stege on Mon, 02 February 2015 13:40
		Re: Hard crash By: Dick Jackson on Mon, 09 February 2015 18:18
		Re: Hard crash By: Jim Pendleton on Mon, 09 February 2015 19:16
		Re: Hard crash By: Lajos Foldy on Fri, 30 January 2015 10:36

Previous Topic:	Exelis Purchased by Harris Corp
Next Topic:	Reopen HDF5 file to add more data?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 18:04:46 PDT 2025

Total time taken to generate the page: 0.00433 seconds