Skip to content

Update jerry API #1147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

LaszloLango
Copy link
Contributor

@LaszloLango LaszloLango commented Jun 15, 2016

JerryScript-DCO-1.0-Signed-off-by: László Langó [email protected]

@LaszloLango LaszloLango added enhancement An improvement api Related to the public API labels Jun 15, 2016
@LaszloLango LaszloLango added this to the Release v1.0 milestone Jun 15, 2016
@LaszloLango LaszloLango mentioned this pull request Jun 15, 2016
13 tasks
* Returns whether the given jerry_value_t is null.
*/
bool
inline bool __attr_always_inline___
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this depends on LTO/all-in-one build, and an API user unlikely to have this advantage.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. This was not a good idea. I'll remove it.

@LaszloLango
Copy link
Contributor Author

@zherczeg, I've upadted the PR. Please check.

* @return true, if invocation was performed successfully, i.e.:
* - no unhandled exceptions were thrown in connection with the call;
* false - otherwise.
* @return TODO
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

return todo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry, I forgot to update the description.

@zherczeg
Copy link
Member

The question is what should happen if we pass error objects as arguments is still open. We definitely need to do something with that before the release.

@zherczeg
Copy link
Member

LGTM

NULL,
args,
1);
if (!jerry_value_is_error (ret_val_print))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ret_val_print should also be released when it's an error, otherwise it may leak.

@LaszloLango LaszloLango force-pushed the jerry-api-update branch 2 times, most recently from 187b446 to 31ca76b Compare June 16, 2016 11:26
@LaszloLango
Copy link
Contributor Author

@dbatyai, I've updated the PR. I will do a big review and update on the function comments in a later PR, but the comments of touched functions should be ready (more or less), so I hope I fixed all of them. :)

 * Fix error handling (related issue: jerryscript-project#1141)
 * Move output paramters to the end of the arguments lists

JerryScript-DCO-1.0-Signed-off-by: László Langó [email protected]
@dbatyai
Copy link
Member

dbatyai commented Jun 16, 2016

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Related to the public API enhancement An improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants