You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jordan (JIRA)" <ji...@apache.org> on 2010/06/20 22:57:23 UTC
[jira] Commented: (THRIFT-807) JavaScript: Initialization of Base
Types with 0 instead of null
[ https://issues.apache.org/jira/browse/THRIFT-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880673#action_12880673 ]
Jordan commented on THRIFT-807:
-------------------------------
The problem I had was not with a numeric return value, but rather a boolean value.
Does you patch fix both?
> JavaScript: Initialization of Base Types with 0 instead of null
> ---------------------------------------------------------------
>
> Key: THRIFT-807
> URL: https://issues.apache.org/jira/browse/THRIFT-807
> Project: Thrift
> Issue Type: Bug
> Components: Compiler (General)
> Affects Versions: 0.3
> Reporter: Roger Meier
> Attachments: THRIFT-807_initialize_with_null.patch
>
>
> I had a problem with the exception avaliable on the tutorial.
> i32 calculate(1:i32 logid, 2:Work w) throws (1:InvalidOperation ouch),
> It couldn't be thrown because initialization of numeric base types is done with 0 instead of null and the checks do compare against null.
> This was not visible with the Tests provided with first patch for JavaScript bindings above, the ThriftTest.thrift definition does not have a combination of a base type return value and an exception.
> I've made a patch that initializes the base types I16,I32, I64 and DOUBLE with null. This could probably solve other issues as well
> Regards
> Roger
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.