You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- id: decrypted_if
type: fmt_oms_apl_vdb
repeat: until
repeat-until: _.next_isnt_vdb
if: not next_isnt_vdb
leading to the following Java:
if (!(nextIsntVdb())) {
this.decryptedIf = new ArrayList<FmtOmsAplVdb>();
{
FmtOmsAplVdb _it;
int i = 0;
do {
_it = new FmtOmsAplVdb(this._io, this, _root);
this.decryptedIf.add(_it);
i++;
} while (!(_it.nextIsntVdb()));
}
}
i is not read and therefore Eclipse provides a warning about that. Is there some way the compiler could recognize that and either don't output i at all or add @SuppressWarnings("unused"). The problem with the latter is of course that if i is read the suppression is wrong and Eclipse warns about that. :-)
The text was updated successfully, but these errors were encountered:
It's not very trivial to do that, but certainly possible. Probably we'll need some precompile-level machinery that will derive whether a particular repeated attribute uses _index or not, and then will use that knowledge to generate that i conditionally.
I have the following KSY:
leading to the following Java:
i
is not read and therefore Eclipse provides a warning about that. Is there some way the compiler could recognize that and either don't outputi
at all or add@SuppressWarnings("unused")
. The problem with the latter is of course that ifi
is read the suppression is wrong and Eclipse warns about that. :-)The text was updated successfully, but these errors were encountered: