Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

function metadata does not handle final arguments

Description

Consider this code:

The metadata given for f is:

Notes:

  • I'm not sure "modifier" is a useful term here. Both access (eg: public) and final are modifiers.

  • you've lost the returntype

For the parameter, the metadata is:

0 out of 5 are correct there. Same for the direct dump of the function.

Environment

None

Attachments

3

Activity

Show:

Adam Cameron 12 August 2024 at 13:32

any idea where’s that’s documented? The following only lists variables,

Erm… well… parameters are variables right? And… erm… where are parameters defined? In the function signature.

I’m being slightly glib there, but equally Adobe ain’t known for clarity of articulation when it comes to their documentation.

Zac Spitzer 12 August 2024 at 13:24
Edited

Zac Spitzer 12 August 2024 at 12:56

Adam Cameron 9 August 2024 at 16:49

does lucee/cfml even support final arguments

Aah… Lucee doesn’t. CFML - as defined by ColdFusion - is supposed to. Since CF2018. Didn’t notice it was just ignoring the final modifier on the parameter when I raised the ticket. soz.

 

This is probably a different issue though, as this ticket is just about how the metadata is reported.

Zac Spitzer 9 August 2024 at 13:24

hmmmm, does lucee/cfml even support final arguments, obviously functions and components do

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 13 August 2021 at 13:36
Updated 12 August 2024 at 13:32