search : decision functions

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

displaying top 100 results

Comment on [ER]: Decision Member functions Support by Aaron N.
[ER]: Decision Member functions Support
3557135 CF-4199859 Suchika S. We have supported Numeric Member Functions . We have separate bugs for decision & formatting functions. Hence , closing this bug.
3557135 CF-4199859 Aaron N. Hi Suchika, CF-4200186 covered numeric member functions. That is closed/fixed. Good. What is the ticket covering all decision functions. Likewise, what is the ticket covering all formatting functions? And all conversion functions. And also the "additional" functions
SauravGhosh CFFiddle for Flow control tags and a few more functions Picking up from where we left off on updating the docs with CFFiddle links, we have now extended the links to the following tag and function categories: File functions Query functions Decision functions Data output functions Flow
3557135 CF-4199859 Adam C. Don't agree with a lot of the decision functions being appropriate, but yes to the others. some thought needs to go into ones like createDateTime. Probably a static method on the DateTime class or something? Not all of these functions are appropriate as object methods
functions Struct functions List functions Date/time functions The next task is to link CFFiddle with Query and Decision functions, and also a few File functions. As always, please use CFFiddle to test the samples. If there are sample(s) that you want to be modified/corrected, share the link […] The post
2609033 CF-3944176 Immanuel N. Fix tested on build, 295680 Test case added, coretests\coldfusion\functions\decision\isvalid\CF-3944176.cfm
" prefix. Compare this to arrays, where all member functions have dropped the "array" method name prefix. I understand that this was probably a decision made to support all three functions... but think about it: Is that really necessary? dateTimeFormat does everything that dateFormat and timeFormat can
, as it claims it's a decision function). It's simply a *formatting* function. * the example code has script comments in tag-based code! * no "History" section It's probably more wrong than it is right. Can you pls not be so half-arsed with your work, and do a thorough, professional job. Have some pride in your
Var.sin() someVar.sqr() someVar.tan() {code} //Decision functions (these should probably be added to all data types?) {code:java} someVar.isArray() someVar.isBinary() someVar.isBoolean() someVar.isClosure someVar.isCustomFunction() someVar.isDate() someVar.isDateObject() someVar.isDateObject() some
as well as operators.Functions would be the constructor as well as an output function (in the example called toString()), which is called when an object is meant to be output. Operators is meaning all kinds of operator types (arithmetic, boolean, decision, string and ternary).See the steps to reproduce
2610298 CF-3712167 External U. No it's not: it's just a very poor language design decision from your team: https://wikidocs.adobe.com/wiki/display/coldfusionen/Defining+components+and+functions+in+CFScript#DefiningcomponentsandfunctionsinCFScript-Specifyingpageencodingpageencoding {quote
to be in step with them (which I think they would be as a matter of course anyhow). The behaviour of the member functions should *not* differ from that of the prodcedural ones though. That would be a poor design decision. -- Adam
Comment on A lot of member functions cannot be chained by External U.
2610071 CF-3733001 External U. +1. The current approach to make tags in script is a poor decision. We don't need tags in script; we need functionality in script - in a well-thought-out-and-consistent syntax. Tag syntax converted to script is just another backwards compatibility blunder we
to be in step with them (which I think they would be as a matter of course anyhow). The behaviour of the member functions should *not* differ from that of the prodcedural ones though. That would be a poor design decision. -------------------------------------------- Aether should fix these language issues
decision based on that code the developer writes and the back-end Java classes used to store the value is an (unimportant) implementation detail. Member functions are IMO syntactic sugar for BIFs, not proper methods on proper objects of any explicit type. If you treat a variable as a date with a date
Number, and LTrim are in the wrong place) - System functions 2) In the "ORM functions" table, the "EntitytoQuery" should be "EntityToQuery" (the "t" should be "T") 3) In the "Decision functions" table, "IsNull" is indented. This indentation before IsNull should be removed
2610071 CF-3733001 External U. Adobe, please reconsider the decision to close this as "Never Fix", or at lease provide some comments to explain this decision. When community members offer constructive criticism of how new functionality can be improved to everyone's benefit, it should
ChangeDelims() being obvious it's a list-specific function *if its case was taken in isolation*, but if one steps back and looks at the bigger picture, it's a poor decision to single out functions that we second guess are / are not ambiguous. Havnig the list prefix (as per the standard functions) unambiguously states
it be through their own poor decisions), than for this function to - basically - be useless. This is not an exercise in pleasing everyone, it's an exercise in making the function work in a way that is logical, predictable, useful, and does what it says on the tin. I think it would be a good idea if you shared
Comment on isCustomFunction() needs to do what it says on the box by External U.
(variables.a, variables.b.clone()); // reference of a is fine; b needs to be a new object though } } This is aI think more obvious, plus has more flexibility as it allows the component to define its own cloning behaviour, rather than a headless function to make that decision globally. Lucee's approach seems to betray
Decision operator inconsistency
2609313 CF-3859758 Rakshith N. As ridiculous as this bug sounds, the decision made is to not fix this bug. My first reaction to this bug was to fix it somehow. We then had a detailed discussion with the engineers and the architect involved to realize the impact of such a fix. The engineers feel
2609859 CF-3756524 Language Adam Cameron Remove "Routines cannot be declared more than once" restriction Related Bugs: CF-3756518 - Similar to There's simply no need for it. Railo allows one to redefine an earlier defined function no problem, so I cannot see why ColdFusion enforces this. Raising
developers with the tools to make their own decision. Which means leaving existing cfinclude functionality alone. If a developer doesn't want a file compiled they can use FileRead() instead - if a developer is specifically including a file over reading it, it should be assumed they know what they are doing
Comment on listChangeDelims() member function missing by External U.
workplaces and it might be a decisive factor as my current company is evaluating CF as its web app development tool of choice. We need to be able to reuse existing Oracle PL/SQL packages and their functions, instead of creating new procedures with OUT parameters! I am a big and loyal fan of CF and am trying
decision right now. The UDF signature must dictate what the UDF can return. If the return type can be optionally-enforced, then the signature needs to say that: Suggestions: - Allows NULL return: `public optional array function f(){}` - Disallows NULL return: `public array function f(){}` Or implement
I see it's a seeming intentional decision (or maybe a mistake): the CFML Reference, for example, has only LINKS to the online docs, where you'd need to go to get the details for each tag/function. Why is this a problem? Well, what if one downloaded the PDF so as to be able to read/search the docs
2608482 CF-4080440 External U. Hey Alex, like I mentioned: "Properties (and functions, and components) have a prescribed notion of metadata, and it makes sense that they can additional attributes." (by properties, I meant , sorry). It's always been documented as *specifically* for providing
, but think about how frustrated that code that works in previous versions is going to effect their decision to continue to develop with ColdFusion in the future. Steps to Reproduce: Write and Index.cfm page that has the following code. session.andrew = 'Hello'; myObj = new test().wtf(); Write a
that the business rules matter-most. Business requirements change at a rapid pace in any life cycle.  It's best the business of the code is at the surface.  Press all the technical stuff down. OOP Continuing on this track: Perhaps impress upong them the value of wrapper functions; classes (Components), pattern
Output(isNull("variables.foo"))//returns YES (bad) writeOutput(isNull("foo"))//throws Variable FOO is undefined. (good) Actual Result: YES YES UndefinedVariableException Expected Result: NO NO UndefinedVariableException 3) Run this: function f() { var someValue = "a" switch(someValue) { case "b": { var foo = "bar" break
CF Elvis Operator does not function as defined.
occurred while invoking an event handler method from Application.cfc. The method name is: OnCfcRequest.’"Which means it never gets the specific exception I threw and therefore I can’t make a decision on what to do based on the exception.I’ve tried to simply rethrow the original exception