tracker issue : CF-4199857

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

[ANeff] ER for: all CF functions to accept named parameters

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff ()

Created: 10/01/2017

Components: Language, Functions

Versions: 2016

Failure Type: Enhancement Request

Found In Build/Fixed In Build: / latest build

Priority/Frequency: Normal /

Locale/System: /

Vote Count: 3

This ER is for: all CF functions to accept named parameters

Denard's idea, as suggested by him in a comment on his ticket CF-4155428:
Additional wishlist item since this was moved from the old bugbase: Support for named parameters to all functions (see Lucee) - most built-in functions currently only support positional parameters - support for named parameters would make the language more consistent while maintaining historical positions for backwards compat



A couple of advantages: (a) defaults don't need to be specified, (b) built-in-functions can be updated/enhanced instead of new functions added [StructSort() could've been enhanced instead of adding StructToSorted()]. Thanks!, -Aaron
Comment by Aaron N.
266 | October 01, 2017 08:00:33 PM GMT
Hi Adobe, I forgot to mention, but it goes w/o saying, ArgumentCollection should also work w/ BIFs as a result of this fix. That's definitely expected behavior. Thanks!, -Aaron
Comment by Aaron N.
27329 | April 07, 2018 08:21:44 PM GMT