You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Andrew Chung (JIRA)" <ji...@apache.org> on 2015/10/10 01:04:05 UTC
[jira] [Updated] (REEF-827) Standardize Java object field access in
InterOp layer
[ https://issues.apache.org/jira/browse/REEF-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Chung updated REEF-827:
------------------------------
Description:
Currently, C++ InterOp code can access a field in a Java object either directly (even if it's {{private}}) with {{GetObjectField()}} or through the (often) {{public}} getter method {{GetMethodId}}. Our code uses a combination of both. We should standardize such that it uses either-or, not both.
Personally, I prefer to use {{GetMethodId}} instead of {{GetObjectField}}.
was:
Currently, C++ InterOp code can access a field in a Java object either directly (even if it's private) with {{GetObjectField()}} or through the (often) {{public}} getter method {{GetMethodId}}. Our code uses a combination of both. We should standardize such that it uses either-or, not both.
Personally, I prefer to use {{GetMethodId}} instead of {{GetObjectField}}.
> Standardize Java object field access in InterOp layer
> -----------------------------------------------------
>
> Key: REEF-827
> URL: https://issues.apache.org/jira/browse/REEF-827
> Project: REEF
> Issue Type: Improvement
> Components: REEF Bridge
> Reporter: Andrew Chung
>
> Currently, C++ InterOp code can access a field in a Java object either directly (even if it's {{private}}) with {{GetObjectField()}} or through the (often) {{public}} getter method {{GetMethodId}}. Our code uses a combination of both. We should standardize such that it uses either-or, not both.
> Personally, I prefer to use {{GetMethodId}} instead of {{GetObjectField}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)