tracker issue : CF-4013671

select a category, or use search below
(searches all categories and all time range)
Title:

Remove restriction on nesting threads

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 06/27/2015

Components: Core Runtime

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 7

See: http://blog.adamcameron.me/2015/06/cfml-i-did-not-realise-one-cannot-nest.html

Basically one cannot nest thread calls.

If there is no *real* reason to prohibit this and it's an artificial restriction on your part... get rid of the restriction.

Raising as a bug because you should never have implemented this restriction in the first place.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4013671

External Customer Info:
External Company:  
External Customer Name: Adam
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

+1 If there is no *real* reason to prohibit this
Vote by External U.
6942 | June 27, 2015 11:29:32 AM GMT
+1 - "To nest threads or not to nest threads, that is the question" - Hamlet
Vote by External U.
6943 | June 27, 2015 02:08:48 PM GMT
This has always seemed like a completely arbitrary restriction and it prevents some very useful types of libraries being written that would help move CFML forward.
Vote by External U.
6944 | June 27, 2015 11:27:14 PM GMT
+1 ......................
Vote by External U.
6945 | September 28, 2015 03:54:33 AM GMT
Can you please confirm in what version of ColdFusion this is going to be implemented in. It says "to fix" but does not say which version.
Comment by External U.
6940 | January 25, 2016 08:19:27 AM GMT
Hello?
Comment by Adam C.
6941 | April 28, 2017 11:48:14 AM GMT
Remove this restriction
Vote by Timothy B.
6946 | February 05, 2018 08:43:33 PM GMT
Is Adobe ever going to address this? Please let us nest threads.
Comment by Dave L.
29125 | June 21, 2018 09:25:03 PM GMT