[
https://issues.apache.org/jira/browse/DERBY-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531182
]
Daniel John Debrunner commented on DERBY-3069:
----------------------------------------------
> I do not believe that varargs change the definition of JPDL.
> However, I believe that varargs can add more candidate methods to JCS.
> So I believe it is that delta to JCS which must be described. Again, does
> that sound correct to you?
I think this all depends on what you intend to implement (or have implemented).
E.g. JPDL could support a varargs declaration in its <Java parameter
declaration list>, not sure if you intend to do this or not, since it's non
standard I can't guess what you are trying to implement, thus it's hard to
review any patch as it's unclear what the intended behave is, beyond a vague
"support varargs" statement.
> Derby does not resolve functions bound to methods with varargs.
> ---------------------------------------------------------------
>
> Key: DERBY-3069
> URL: https://issues.apache.org/jira/browse/DERBY-3069
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0, 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-3069-01-varargs-aa.diff,
> derby-3069-01-varargs-ab.diff, z.java, z.sql
>
>
> Varargs were added in Java 5. It would be nice if Derby let you invoke a
> function bound to a method with a variable length argument list. The
> Reference Guide states a small number of restrictions for methods which can
> be invoked as Derby functions: They must be public, static, and not have
> arguments which are long datatypes. I see no reason that Derby shouldn't be
> able to resolve and invoke functions which are bound to methods which don't
> suffer these limitations but which have variable argument lists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
