Better(?) late than never: CF.Objective() recap

G'day:
I'd kinda decided it was too late in the piece to write this article now, given CF.Objective() was a month ago. Sorry for not writing it up in a timely fashion, but I had a motivation block for a coupla weeks after returning from it. The timing of this blockage was coincidental, and nothing to do with CFO itself.

However I am going to offer some feedback now due to a comment from Jason Dean y/day:

90 ppl in my session at #cfobjective. 14 filled out a session survey. Overall, surveys weren't completed. What does it take? #disappointed
— Jason Dean(12Robots) (@JasonPDean) June 11, 2014

CFML: arraySetEach()

G'day:
I had a conversation on IRC the other day with Jason Dean about a shortcoming of arraySet().


The issue is that array set works like this:

arraySet(array, from, to, value)

So like this:

sameStructs = [];
arraySet(sameStructs, 1, 5, {});
sameStructs[3].foo = "bar";
writeDump(sameStructs);

Unfortunately - as you might guess from the variable name - ColdFusion only evaluates the value once - meaning each array element has the same structure. So this code outputs:

Censorship on Adobe ColdFusion forums - Open letter to the management of the Adobe ColdFusion forums

Open letter to the management of the Adobe ColdFusion forums
(I do not know how to contact you, but I will try to find out and send this to you directly as well, as a courtesy).

Update:
Adobe have been in touch with me regarding this.

Further Update:
This issue has now been resolved.

Cookies can actually be set after a CFLOCATION...

G'day:
I seem to have more verbal diarrhoea than usual today.

I was reading a posting on Jason Dean's blog this morning, about being able to set cookies in conjunction with <cflocation>.  Back in the bad old days this wasn't possible because of the way <cflocation> worked, but this has not been the case for some time (which is what Jason is saying in his blog).

One of the comments was asking about whether it was possible to set a cookie after a <cflocation> call, which Jason clarified one could not.  This isn't because of a vagary of cookies and <cflocation>, it's because once a <cflocation> is encountered, ColdFusion stops processing any further code.  It's kinda like a GOTO.