| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two functions in here:
* addressOf: Extremely useful when debugging a gjs process with a
native code debugger like GDB. Add "print(imports.system.addressOf(foo))"
for an object, then take the number it prints "12345" and paste into
gdb like:
p (JSObject*) 12345
* breakpoint: Wrapper for G_BREAKPOINT(). Insert a SIGTRAP which,
if the process is under a debugger, causes a breakpoint. Combines
nicely with the above.
|
|
|
|
| |
Octal appears to be deprecated in XULRunner 1.9.3.
|
|
|
|
|
| |
We do modify it inside dbus.js. Older spidermonkey seemed not
to care, but with xulrunner 1.9.3, modifications silently fail.
|
|
|
|
|
|
|
|
| |
JS_PushArgumentsVA vanished in 1.9.3; since it was only used in
debugger.c, which was itself just removed, delete it.
Separated from a larger patch by
Colin Walters <walters@verbum.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 1.9.3, we need to explicitly say when we're making the global
object. Clean this up by introducing a wrapper function; while
we're at it, also call JS_InitStandardClasses here since everything
else creating a global did too.
Note that rooting the global object is not necessary, so remove
that. From a grep of the sources (going back to at least 1.9.2):
./src/jsgc.cpp: if (acx->globalObject && !JS_HAS_OPTION(acx, JSOPTION_UNROOTED_GLOBAL))
./src/jsgc.cpp: JS_CALL_OBJECT_TRACER(trc, acx->globalObject, "global object");
|
|
|
|
|
|
|
|
|
|
| |
The two have always been conceptually distinct types. Even in 1.9.3,
they are still the same in implementation, but to avoid a pile of
warnings, we should avoid confusing them. Unfortunately, even the
SpiderMonkey docs are wrong in a few places, so gjs' code confusing
them is understandable.
Anyways, fix up places that made this assumption.
|
|
|
|
| |
Use C NULL where it's expected, not JSVAL_NULL.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=622896
|
| |
|
|
|
|
|
| |
This function isn't intended for normal numeric conversions: see
https://developer.mozilla.org/en/JS_NewNumberValue
|
| |
|
|
|
|
|
|
|
| |
These very simple js tests exercise the basic infrastructure, before
we drop into more complex unit tests.
Added for XULRunner 1.9.3 porting.
|
|
|
|
|
| |
Trying to narrow down a XULRunner 1.9.3 hang, and didn't see
this simple test case anywhere else.
|
|
|
|
|
| |
For XULRunner 1.9.3 we'll need to fix this code, so ensure we only
need to fix it in one place.
|
|
|
|
|
|
| |
Hopefully temporary. See:
https://bugzilla.gnome.org/show_bug.cgi?id=616193
|
|
|
|
|
| |
Might as well do this here instead of having random tests do it;
we link to GObject anyways.
|
|
|
|
|
|
|
| |
There's no ordering for g_dir_read_name, we're likely to get
filesystem order. Since that is a pain for reproducibility, and
we want to sort some tests before others (so we can increase
in complexity), define it via strcmp().
|
|
|
|
|
|
|
| |
Exposing the error hook to JS was a cute hack, but the way it's
implemented is problematic; see
https://bugzilla.gnome.org/show_bug.cgi?id=630179
|
|
|
|
|
|
|
|
| |
for methods with an empty out signature.
I broke this with https://bugzilla.gnome.org/show_bug.cgi?id=629965
https://bugzilla.gnome.org/show_bug.cgi?id=629967
|
|
|
|
|
|
|
|
|
|
|
| |
instead return []
This is a problem for asynchronously implemented methods with an empty
in-signature. Without the fix they are called with
methodAsync(undefined, dbusCallback) instead of the expected
methodAsync(dbusCallback);
https://bugzilla.gnome.org/show_bug.cgi?id=629965
|
|
|
|
| |
Was broken by prefixing of nodist_.
|
|
|
|
| |
This should have been in the earlier single-includes patch.
|
|
|
|
| |
Avoids a compiler warning.
|
|
|
|
| |
Seems useful, and having it static-but-unused causes a warning.
|
|
|
|
|
|
| |
As far as I can see GCC simply isn't inferring that one boolean
is always set in the failure flow path, but initializing these
anyways is good practice.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The previous approach of "Warn when including an individual header"
is obviously lame, since the warnings weren't being fixed.
The better way here is to do what all the rest of the G stack does;
disallow single includes externally, allow them internally via a
GJS_COMPILATION flag.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=625090
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=625090
|
|
|
|
|
|
|
| |
When throwing because only null-terminated arrays are supported, the
return value was unitialized memory.
https://bugzilla.gnome.org/show_bug.cgi?id=629693
|
|
|
|
|
|
|
|
| |
gobject-introspection has been changed so that g_arg_info_get_closure()
and g_arg_info_get_destroy() now count from the first parameter for
both functions and methods; the indexes never include 'self'.
https://bugzilla.gnome.org/show_bug.cgi?id=628999
|
|
|
|
| |
Funny GCC doesn't warn about this at -O0...
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=627383
|
|
|
|
| |
We switched to the new test API.
|
|
|
|
|
|
|
|
|
| |
Everything is now Regress, and both it and GIMarshallingTests come
in .c form.
Disable the g_utf8_get_char test until gunichar becomes introspectable.
https://bugzilla.gnome.org/show_bug.cgi?id=627435
|
|
|
|
|
| |
The code used variations of guint32 or unsigned int when what
was expected was "gsize", a possibly 64 bit value.
|
|
|
|
|
|
|
| |
gjs_dbus_proxy_call_json_async does not allow a{sv} arguments
which need access to the message, so make this public
https://bugzilla.gnome.org/show_bug.cgi?id=627315
|
|
|
|
|
|
| |
Otherwise the build fails.
Bug #626672
|
| |
|
|
|
|
|
|
| |
See bug 623774.
https://bugzilla.gnome.org/show_bug.cgi?id=623775
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
docs/gjs-byte-array.txt explains how to use it and its features.
The primary purpose of this for now will be to bind C APIs that use
byte buffers, such as read and write operations. As such, the
ByteArray class is pretty simple and is mostly just a blob you can
shovel between C APIs.
In the initial patch, ByteArray does not even support array operations
such as slice().
The enumeration support relies on defining each byte as a property
on the byte array object, which makes enumerating bytes in the array
even more inefficient than it already would be.
https://bugzilla.gnome.org/show_bug.cgi?id=571000
|
|
|
|
|
|
|
|
| |
Allow native modules to be registered inside gjs.so.
This will be used by a few modules like sys (needs argv) and
byteArray (exports internal api to gi)
https://bugzilla.gnome.org/show_bug.cgi?id=622071
|
| |
|
|
|
|
| |
Use type names instead of types to avoid a glib 2.22 dependency
|
| |
|
|\ |
|