comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Copying a hash

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

Re: Copying a hash [message #81099 is a reply to message #81003]

Mon, 06 August 2012 16:41

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

Paul van Delst writes:

> Bummer. To be honest, I'm not sure what the correct behaviour should be. Recursively copy all the components? I guess if
> we think of the numbers and strings as objects also, then the answer should probably be yes.... ? Why duplicate one type
> of object (int, float, or string) but not another (hash or list)? Still... it just doesn't seem right.

I think this takes us back to the need for a "deep copy" in objects.

http://www.idlcoyote.com/tips/copy_objects.html

But, we have only been requesting it for 9 years, I see by
the date on the article. I think the standard is 12 years
before they either fix the problem or consign the requester
to the loony bin. :-)

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")

Report message to a moderator

[Message index]

		Copying a hash By: Matt[3] on Mon, 06 August 2012 13:54
		Re: Copying a hash By: Matt Francis on Thu, 09 August 2012 17:44
		Re: Copying a hash By: Bob[4] on Fri, 17 August 2012 15:25
		Re: Copying a hash By: Matt[3] on Thu, 09 August 2012 11:25
		Re: Copying a hash By: Matt[3] on Tue, 07 August 2012 08:44
		Re: Copying a hash By: David Fanning on Mon, 06 August 2012 16:41

Previous Topic:	RESOLVE_ROUTINE not finding MEDIAN function?
Next Topic:	mosaic

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 30 15:24:35 PST 2025

Total time taken to generate the page: 1.04474 seconds