| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/svaarala/duktape/blob/master/doc/release-notes-v2-0.rst#duk_error-duk_error_va-duk_throw-duk_fatal-have-a-return-value
This change suppress warnings about ignoring the return value.
However, it looks like we should be returning error in these cases
rather than continuing.
I'll do that in a separate commit.
|
|
|
|
| |
https://github.com/svaarala/duktape/blob/master/doc/release-notes-v2-0.rst#duk_safe_call-userdata
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Kinnison did all teh heavy tjinking on this!
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the binding to omit specifying code for class property
getters and setters. The omitted code will be generated by genbind to
directly call suitable libdom accessors.
The type of the property (string, boolean etc.) is derived from the
IDL. If this type is incorrect, or is a type the generator cannot
automatically produce, then the property will be treated like it has no
binding implementation and generate unimplemented warnings.
|
| |
|
|
|
|
|
|
|
|
|
| |
interface attributes with the putforwards extended attribute call the
setter specified in that extended attribute.
The WebIDL is supposed to ensure the attribute is readonly before
allowing a putforwards but we only warn about this as there are
several examples where readonly is omitted.
|
|
|
|
|
| |
Uses annotated AST to put line directives in the generated source so
any code errors in the binding can be easily located.
|
| |
|
|
|
|
|
|
| |
Instead of c types being opaque strings this makes the bindig parser
understand them. This is necessary for extended attribute parsing in
future but also makes the binding more easily understandable.
|
|
|
|
|
|
| |
It appears that string parameters to operations must be coerced from
other types instead of throwing a type error to conform to expected
behaviour.
|
|
|
|
|
|
| |
This generates routines which correctly handle reading a member from a
dictionary and returning it as the correct c type. Currently the types
"any", "user" and "sequence" remain unhandled.
|
| |
|
|
|