search : code reuse

2609687 CF-3804384 External U. No need to reiterate what others have said. This is an impact to code reuse and portability and should be modified to be consistent across the board.

2609785 CF-3773095 External U. +1 to Sean's analysis. Code reuse and consistency

2609785 CF-3773095 External U. I think it would be great for the language to allow VAR outside of CFCs. Template-local would be ideal, but VARIABLES would be fine too. Disallowing VAR declarations just feels arbitrary - allowing it would improve code reuse and consistency.

, then select and copy the text to finally open the destination document and paste the code. What if I could save that block somewhere in my favorite editor (CF Builder) and then invoke it whenever I […] Blog,Code Reuse,ColdFusion,ColdFusion Builder,snippets

Comment on OSGi Support is Needed to Assure Secure Code by Charlie Arehart

2673189 CF-4147159 Piyush K. Aaron, The fix for bug # CF-4126642 is due to be released with next CF update. But you've mentioned that you can experience the issue even with the use of system setting: -Dcoldfusion.udf.reuseTagInstances=false Can you pls. share the relevant code extract with which

CFScript was implemented in CF 4.0 Tags seemed ok back then because pre CFC’s (CF Components) Used UDF’s and Custom Tags to reuse and separate code CF MX (6.0) brought about CFC’s so separation of code CFCs – you create methods, which are ColdFusion […] Blog,cfscript,closures,elvis operator,first class

+ spreadsheet functions, which you need to be logged in to consume in your workspace. Other than a few categories of functions, where external and multiple files are involved, you can very well use and reuse code snippets as an anonymous user.

-critical because without it we lose the ability to use custom tags without building a tag-based cffunction wrapper to access them. Without this, a critical portion of ColdFusion's code reuse and high-level funcitonality is gone for those using script-based syntax. Case in point: Model-Glue uses a custom tag

Bug 80780:CF9 does not allow for sql parameter REUSE

2608469 CF-4087803 External U. I could make use of this, I have run into cases where I had to use javaloader because I can't rely on the application specific settings for the classpath. It allows developers to write more modular code. Bonus feature would be to have a create

)); Steps to reproduce: Just run the above code twice. Actual result: exception: "A timeout occurred while attempting to lock lock2." Expected result: "object 2" displayed Workaround: JVM arg -Dcoldfusion.udf.reuseTagInstances=false Related ticket: 4044261 ----------------------------- Additional

workaround: JVM argument -Dcoldfusion.udf.reuseTagInstances=false I've confirmed that workaround resolves this issue, using the following code which displays incorrect result in CF2016 final unless using that JVM argument: SELECT parentID, title, sitePageID FROM variables.myQuery WHERE parent

2596827 CF-3616590 External U. Remember that everything was tag-based original and so string interpolation used the expression parser from the tag-based world, along with cfset and cfif etc so everything was consistent. cfscript is essentially a whole separate parser but clearly reuses

4188046 CF-4201938 ALEXANDER H. What is the solution / bugfix to the performance issue? With array we only said what type of speed and memory usage we expect. Exponential memory usage with id‘s in a single row is not ok nor logic. The code is EXTREME slow. Sooo slow and memory intensive

new rows, etc. * Uses the same approach that every ColdFusion developer knows. It is easier for developers to apply expressions to and format query outputs. * Enables much greater code re-use:At my current workplace we re-use 95% of our report code to generate reports in PDF, HTML and Excel

; that they chose to reuse the previous attribute name is only unfortunate for you (and the likely few who were subsequently using that attribute incorrectly). If Macromedia/Adobe had written CF6+ to throw errors if the obsolete variable was being used (rather than just ignoring it), your code would have had

6502588 CF-4206045 Jonathan C. "So the question arises why you would want to use such a design. " I don't believe your analysis of the code sample is looking at real-world programming examples. CFML Developers have been scoping static methods (UDFs) in to the application scope, for re-use in all

6502588 CF-4206045 A. B. Hi Jonathan, Yes, I agree that "a closure, when scoped should be treated as a static variable". And, yes, given the code application.myClosure = function () {} I agree with your point that application.myClosure "itself would be static and no attempt at garbage

.cfm ---------------------- SERVER.delete("results"); SERVER.results=[]; for(i=1; i mypage.cfm ---------------------- if(FORM.count()) { lock name="myLock" type="exclusive" timeout=10 { if(FORM.count()) { SERVER.results.append(duplicate(FORM)); } } } Steps to reproduce: Just run the above code

:Harry Klein Note Added: The latest path did not resolve this issue, the setting is still needed Date Added :2016-02-16 09:47:47.0 Added By: PreRelease User User Name:Harry Klein Note Added: Thanks for your help! I can confirm that the setting -Dcoldfusion.udf.reuseTagInstances=false in jvm.conf solves