polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Merlin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZEST-122) Use parameter names to build better error messages on null barrier faults
Date Sun, 03 Jul 2016 15:27:11 GMT

    [ https://issues.apache.org/jira/browse/ZEST-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360574#comment-15360574
] 

Paul Merlin commented on ZEST-122:
----------------------------------

It turns out that parameter names are not included in bytecode by default.
One need to compile using {{-parameter}}.
So this issue is more about supporting parameter names when they are enabled and falling back
to previous behaviour if not.

> Use parameter names to build better error messages on null barrier faults
> -------------------------------------------------------------------------
>
>                 Key: ZEST-122
>                 URL: https://issues.apache.org/jira/browse/ZEST-122
>             Project: Zest
>          Issue Type: Improvement
>            Reporter: Paul Merlin
>             Fix For: 3.0
>
>
> Parameters to composite's methods must be non-null by default. This can be relaxed using
the @Optional annotation.
> This issue is about producing more meaningful error messages, ie. including the parameter
name, when a null parameter is given to a composite's method.
> See https://docs.oracle.com/javase/tutorial/reflect/member/methodparameterreflection.html
for details on parameter names reflection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message