| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=699532
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=699531
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=699531
|
| |
| |
| |
| |
| |
| | |
This fixes a compiler warning when using -Wmissing-format-attribute.
https://bugzilla.gnome.org/show_bug.cgi?id=698521
|
| | |
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=699442
|
| |
| |
| |
| |
| |
| | |
Just because they both start with 'cl'.
https://bugzilla.gnome.org/show_bug.cgi?id=698090
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
It's breaking the gjs test suite
https://bugzilla.gnome.org/show_bug.cgi?id=698698
|
| |
| |
| |
| |
| |
| |
| |
| | |
Nobody is really known to still use g-i with python 2.5, support
for 2.5 gets broken every now and then in the tree because nobody
is paying much attention any more so just drop it.
https://bugzilla.gnome.org/show_bug.cgi?id=698617
|
| |
| |
| |
| |
| |
| |
| |
| | |
a09072bd1f75dfc7497ed599e03e331bff411fd4 introduced new symbols in
tests/scanner/regress.[ch] but was missing the expected generated
documentation.
https://bugzilla.gnome.org/show_bug.cgi?id=698616
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Configure with --enable-doctool when running "make distcheck"
- Remove $(top_builddir)/.make-check-passed as the pre-commit hook
using this was removed in de84ea0cf212c251e099f456bb675492f664e93d
- Fix CLEANFILES + manual rm invocations
- Fix running warning tests uninstalled (VPATH build issue)
https://bugzilla.gnome.org/show_bug.cgi?id=697669
|
| |
| |
| |
| |
| |
| |
| | |
${enable_tests} was removed in f5631640751b5a998b3616db78dd5dcd9ee62126
so there's nothing left to report about...
https://bugzilla.gnome.org/show_bug.cgi?id=697669
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the spirit of c9708af2 also parse and ignore
__asm [whitespace] volatile
__asm__ [whitespace] volatile
__volatile
__volatile__
Ignoring __volatile is cosmetic, but the __asm cases avoid an unwanted
VOLATILE token. Extension of
https://bugzilla.gnome.org/show_bug.cgi?id=678794
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=698438
|
| |
| |
| |
| | |
See https://bugzilla.redhat.com/920595
|
| |
| |
| |
| |
| |
| |
| | |
As seen in xlib.gir at least; this is something we should probably ban
though.
https://bugzilla.gnome.org/697759
|
| |
| |
| |
| |
| |
| |
| | |
vala generates this, and we need to honor it now that we're using the
c:prefix as an optimization when searching for gtypes.
https://bugzilla.gnome.org/697759
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For example, GTK+ has over 15.000 comment blocks (/* ... */)
of which only about 5.000 are GTK-Doc comment blocks (/** ... */).
No need to store and parse those +-10.000 comment blocks
just to find out we don't care about them anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=697625
|
| |
| |
| |
| |
| |
| | |
mktemp was deprecated in Python 2.3...
https://bugzilla.gnome.org/show_bug.cgi?id=697624
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=697621
|
| |
| |
| |
| |
| |
| |
| | |
The XML specification clearly states it's xml:space
http://www.w3.org/TR/xml/#sec-white-space
https://bugzilla.gnome.org/show_bug.cgi?id=628739
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
g-ir-scanner can be a bit on the slow side. While true we
now do a bit more work parsing GTK-Doc comment blocks and
more is still to come, one of the biggest hotspots besides
what's going on in _giscanner.SourceScanner() comes from
the OrderedDict implementations we have been using.
For example, time needed to build Gtk-3.0.gir on a relatively
slow machine using "python2 -m cProfile -o $prefix/bin/g-ir-scanner ...":
1) Our original DictMixin sublass:
92,79867 seconds
2) Python's collections.OrderedDict class:
88,65786 seconds
3) Larosa/Foord implementation from http://www.voidspace.org.uk/python/odict.html :
71,64323 seconds
4) SqlAlchemy's implementation:
66,12449 seconds
Looks like we have a clear winner with the SqlAclchemy
implementation, which comes in at around 20 seconds
without profiling on the same machine. Not bad.
https://bugzilla.gnome.org/show_bug.cgi?id=697620
|
| |
| |
| |
| |
| |
| | |
use the documented __exit__ signature instead
https://bugzilla.gnome.org/show_bug.cgi?id=697619
|
| |
| |
| |
| |
| |
| | |
It's more readable and as an added bonus Python 3 compatible.
https://bugzilla.gnome.org/show_bug.cgi?id=697616
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=697615
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During review Colin Walters mentioned:
"""
One thing I should probably explain is my habit of *always* passing a
tuple for %. The reason is pretty simple...a long time ago I had an
error handler that did: print "unexpected data: %s" % foo. And I'd
changed the type of "foo" from a string to a tuple at some point.
But this obviously caused "print" to fail because it was expecting
multiple format strings.
Basically always using tuples is safer in case you change the type
of a variable to a tuple.
"""
This fixes violations of this rule introduced up until now.
https://bugzilla.gnome.org/show_bug.cgi?id=697614
|
| |
| |
| |
| |
| |
| | |
Changed by accident in 2df621c53cdffbc3c43c3745947ee859020c8338
https://bugzilla.gnome.org/show_bug.cgi?id=697613
|
| |
| |
| |
| |
| |
| | |
Removed by accident in 2df621c53cdffbc3c43c3745947ee859020c8338
https://bugzilla.gnome.org/show_bug.cgi?id=697612
|
| | |
|
| | |
|
| |
| |
| |
| | |
Just more efficient.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When g_irepository_find_by_gtype() doesn't succeed on a simple prefix
match (the current 'fastpass' mechanism), it ends up taking a
considerable amount of CPU time, traversing the contents of all typelibs.
I imagine that the reasons to have the exhaustive search fallback are
not as strong as they used to be. For example, the case mentioned
(Clutter including Cogl) no longer seems to be true.
Also, typelibs (as generated by g-ir-scanner) now provide
comma-separated C prefix info for cases when the typelib includes
introspection info for multiple prefixes. For example, the Sugar typelib
has a c_prefix string of Sugar,EggSM,Gsm,Acme. So I imagine there are
not many remaining justified cases where the exhaustive search is needed.
With that in mind, I found two ways to optimize this function:
1. Support comma-separated C prefixes
2. Don't bother with an exhaustive search if we did find a typelib
claiming support for the prefix. For example, if we're looking for
GdkDeviceManagerXI2 (currently non-introspectable) and we already found
typelib files providing the 'Gdk' prefix that didn't offer this, lets
not bother with the exhaustive search, we aren't going to find anything.
|
| |
| |
| |
| | |
Spotted by Coverity
|
| |
| |
| |
| |
| |
| |
| | |
Change mistaken return type of GIMarshallingTestsFlags to
GIMarshallingTestsEnum in vfunc_return_enum.
https://bugzilla.gnome.org/show_bug.cgi?id=637832
|
| |
| |
| |
| |
| |
| |
| |
| | |
They could be freed in separate threads (e.g. language binding GC
thread). But no particular reason to change other than noticing it
during code inspection for a different bug.
https://bugzilla.gnome.org/show_bug.cgi?id=688694
|
| |
| |
| |
| |
| |
| |
| | |
Commit 9a1e0c63c13f3567e75553d2d07dd914d5b81287 broke this as
os.name doesn't return 'OpenBSD', but 'posix'
https://bugzilla.gnome.org/show_bug.cgi?id=696765
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Copy cairo-1.0.gir, which is now built during the introspection building
process.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Add vfuncs and methods for an object returning an enum or
using one as an output argument.
https://bugzilla.gnome.org/show_bug.cgi?id=637832
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use a simple Python script that uses Python REGEX abilities to create
cairo-1.0.gir from cairo-1.0.gir.in with the correct values for Cairo, for
use in the Visual Studio builds of g-i. It can be later extended if
needed.
Also dist this, and call this script from gengir.bat so that cairo-1.0.gir
and cairo-1.0.typelib can be built and "installed"
https://bugzilla.gnome.org/show_bug.cgi?id=692165
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This helps reproduce the issue with spidermonkey's .pc file using
-include.
Also add a single quote test case.
https://bugzilla.gnome.org/show_bug.cgi?id=695182
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Newer spidermonkey .pc file contains a -include argument, which
g-ir-scanner doesn't understand. Rather than us attempting to replicate
all of cpp's options, use wrapper arguments in Makefile.introspection
to pass them through.
https://bugzilla.gnome.org/show_bug.cgi?id=695182
|
| |
| |
| |
| | |
Previous commit introduced the flaw.
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=695182
|
| |
| |
| |
| |
| |
| | |
Doesn't work with arguments that have shell quotes.
This reverts commit 95b03cf87efbd4fea4b7d55601c9752cefd29bfc.
|