Comments on: The Inner Workings of a ColdFusion Array and Structure

By: Jimmy

Jimmy — Thu, 13 Aug 2009 16:48:39 +0000

Thanks a lot for this! It just saved me a bunch of time. I wasn’t aware of CF holding a single copy of an array/struct in memory if you make a copy of it. I was ending up with 7 arrays with the same data and I couldn’t figure out why. Thanks!

By: Inner Workings of ColdFusion Arrays and Structures « Ecoders Resource

Inner Workings of ColdFusion Arrays and Structures « Ecoders Resource — Mon, 22 Sep 2008 03:59:16 +0000

[...] http://www.simonwhatley.co.uk/the-inner-workings-of-a-coldfusion-array-and-structure Tags: arrays, ColdFusion, reference, struct, structure, value [...]

By: Sergey

Sergey — Mon, 12 May 2008 17:46:29 +0000

Very nice article, thanks

By: Simon

Simon — Wed, 12 Mar 2008 10:47:51 +0000

@Duncan you’re entirely correct. I’ve updated the post.

Clearly writing this post late at night was not a very clever idea!

By: duncan

duncan — Wed, 12 Mar 2008 10:42:39 +0000

Either I'm being daft, or there's a mistake in your code or comments:

a change in b.name will also result in a change of a.name: a.name = "Simon Whatley"; b = a; //shallow copy for Struct b.name = "John Doe"; writeOutput(a.name); // the returned result is Simon Whatley

Should the comment say John Doe?

a = structNew(); a.name = "Wu Mingshi"; b = duplicate(a); //deep copy for Struct b.name = "Ivan Ivanovic"; writeOutput(a.name); // the returned result is Ivan Ivanovic

Shouldn't this comment say Wu Mingshi?

By: injun #576871

injun #576871 — Tue, 11 Mar 2008 14:17:13 +0000

Good post!
PS: thanks for ‘Ivan Ivanovic’…