Support for CF 11?

15 views
Skip to first unread message

Sn3akyP3t3

unread,
Jul 23, 2014, 11:55:43 AM7/23/14
to cfreg...@googlegroups.com
I'm running through our resources we currently utilize and see that cfRegEx isn't yet officially listed to support CF11.  I'm suspecting there won't be any issue, but I would like to verify prior to blindly changing dependencies.  Thanks Peter!  Projects like these get underappreciated, yet are quite essential to those that do use them!

Peter Boughton

unread,
Aug 2, 2014, 12:16:54 PM8/2/14
to cfreg...@googlegroups.com
Hey Pete, sorry for the slow reply; I've got a lot on at the moment. Many thanks for the appreciation - it is indeed nice to hear that it's useful! 

I'm not aware of any changes with CF11 that affect cfRegex, but I haven't specifically tested it yet either. (I will do so, but the download will take at least an hour, so I'll respond again later.)

However, I would strongly recommend against using CF11.0 - it was a rushed release for an arbitrary deadline, and I don't consider it finished/stable software. My advice is not to bother evaluating it at least until the first significant update has been released.

Peter Boughton

unread,
Aug 2, 2014, 1:35:47 PM8/2/14
to cfreg...@googlegroups.com
Ok, so all the tests that run on CF10 also run on CF11 Express 64-bit.

I also checked Railo 4.2.1.000, and that works so long as the "Null Support" setting is left on CFML default (otherwise various StructKeyExists calls return incorrect values).

Sn3akyP3t3

unread,
Aug 3, 2014, 5:35:04 PM8/3/14
to cfreg...@googlegroups.com

Thanks Peter for pushing that through testing!  I wasn't aware that stability of CF 11 is a risk.  I'll be sure to bring that up as a concern prior to going forward with upgrade.  Any sources where I should be putting my ears on for the all clear on that?

Peter Boughton

unread,
Aug 4, 2014, 4:12:01 PM8/4/14
to cfreg...@googlegroups.com
Well there's various issues, but to sum it up: CF11 broke both FW/1 and ColdBox, probably the two biggest CF frameworks around. That should indicate how well Adobe tested it.

I basically agree with what Adam says in these two articles - it should be considered a second beta and not a full release:

Adam's blog is probably the best place to keep track of when the first update arrives and whether it actually solves things.
Reply all
Reply to author
Forward
0 new messages