Title:
Bug 84164:(Watson Migration Closure)Replace "noCase" functions by a parameter for case sensitive functionsSurely people are already used to find() and findNoCase() and similar functions and they are used in every application, but why no
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Sebastian Zartner / Sebastian Zartner (Sebastian Zartner)
Created: 09/14/2010
Components: Language, Functions
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Minor / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
Replace "noCase" functions by a parameter for case sensitive functionsSurely people are already used to find() and findNoCase() and similar functions and they are used in every application, but why not combine this functionality in one function + "caseSensitive"/"noCase" parameter?Since every version of CF integrates more functions and thereof becomes more complex and because people starting with CF (as of my experience) normally oversee, that case sensitive and case insensitive functionality is seperated into two functions, I am suggesting to combine similar functionality in one function.Of course this couldn't be done in one version, so all case sensitive functions like find(), compare(), replace() etc. would first get a new parameter controlling the case sensitivity and all "noCase" functions would be marked as deprecated. In a second step the "noCase" functions would be removed completely.
Method:
<!--- In the following example "pos" will be 5 ---><cfset pos = find("ColdFusion", "fusion", 1, false> <!--- last parameter is "caseSensitive" --->
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3042163
External Customer Info:
External Company:
External Customer Name: Sebastian Zartner
External Customer Email: 4E7365D64550DB12992015D5
External Test Config: 09/14/2010Attachments:
Comments: