| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
On bug #719966, the question arose of whether parameters annotated with
(element-type) but not (not nullable) are regarded as nullable or
non-nullable.
Add some new unit tests to Regress-1.0.gir to check the behaviour is as
expected: annotating a parameter with (element-type) implicitly makes it
non-nullable (unless also annotated with (nullable)).
https://bugzilla.gnome.org/show_bug.cgi?id=757678
|
|
|
|
|
|
|
|
| |
Use a single static allocation for the hash created in regress_test_ghash_gvalue_return().
This function is explicitly marked as returning the hash with transfer-none
and doesn't need to re-create the hash each call.
https://bugzilla.gnome.org/show_bug.cgi?id=736517
|
|
|
|
|
|
| |
Transfer is annotated as full so the function should free its input.
https://bugzilla.gnome.org/show_bug.cgi?id=736517
|
|
|
|
|
|
|
| |
Transfer is annotated as full so the function should free its input
after testing and before output assignment.
https://bugzilla.gnome.org/show_bug.cgi?id=736517
|
|
|
|
|
|
|
|
| |
g_simple_async_result_complete_in_idle() will add its own reference for
managing the async result. We need to unref the result after calling this
so we don't leak.
https://bugzilla.gnome.org/show_bug.cgi?id=736517
|
|
|
|
|
|
|
|
|
|
| |
g-ir-scanner now supports something like this:
typedef void my_callback(int);
Notice how my_callback is not a pointer.
https://bugzilla.gnome.org/show_bug.cgi?id=755645
|
|
|
|
|
|
|
| |
The nullable code needs to search via index lookup of closure_name,
which drops the need to (incorrectly) assign closure_name again.
https://bugzilla.gnome.org/show_bug.cgi?id=756352
|
|
|
|
|
|
|
| |
Fixup to commit 10cb665fee2cc378dd2f13bad16e6384836a8b16. I failed to
work git properly when submitting the patch.
https://bugzilla.gnome.org/show_bug.cgi?id=729660
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gpointer parameters and return types should be marked as nullable by
default, unless:
• also annotated with (type) and not with (nullable); or
• explicitly annotated with (not nullable).
This introduces the (not nullable) annotation as a direct opposite to
(nullable). In future, (not) could be extended to invert other
annotations.
https://bugzilla.gnome.org/show_bug.cgi?id=729660
|
|
|
|
|
|
|
|
| |
All user_data pointers should be nullable, and they should all be
annotated as closures too. I have not found any counter-examples where a
closure is non-nullable.
https://bugzilla.gnome.org/show_bug.cgi?id=729660
|
|
|
|
|
|
|
|
| |
The optional annotation was being applied which
is invalid for return values.
https://bugzilla.gnome.org/show_bug.cgi?id=752029
Signed-off-by: Garrett Regier <garrett.regier@riftio.com>
|
|
|
|
|
| |
Apparently Python 2 still tries to interpret r"\u" in some
circumstances?
|
|
|
|
|
|
| |
Add conditional import for Python 3's renamed builtins module.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add unicode_literals future import which turns any string literal
into a unicode string. Return unicode strings from the Python C extension
module. Force writing of annotations (g-ir-annotation-tool) to output utf8
encoded data to stdout.
This is an initial pass at following the "unicode sandwich"
model of programming (http://nedbatchelder.com/text/unipain.html)
needed for supporting Python 3.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
| |
Use future import "print_function" and update relevant uses of print
as a function call. See: PEP 3105
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
|
|
|
|
| |
Import Python 3 compatible "true division" from the future (PEP 238).
This changes the Python 2 classic division which uses floor division
on integers to true division. Verfied we don't actually use the
division operator anywhere in the code base so this a safety for
supporting both Python 2 and 3.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
|
|
|
|
|
| |
Use absolute_import to ensure Python 3 compatibility of the code base.
https://bugzilla.gnome.org/show_bug.cgi?id=679438
|
| |
|
|
|
|
| |
More followup to https://bugzilla.gnome.org/show_bug.cgi?id=752047
|
|
|
|
| |
This reverts commit 232f3c831260f596e36159112292897962a505b4.
|
|
|
|
|
|
| |
It broke at least atk and mutter.
This reverts commit 5ae7bd58b6266997b61d897ad6562118eeb59210.
|
|
|
|
|
|
|
|
| |
This is an issue in various code bases and tends
to confuse newcomers.
https://bugzilla.gnome.org/show_bug.cgi?id=752047
Signed-off-by: Garrett Regier <garrett.regier@riftio.com>
|
|
|
|
| |
Related to: https://bugzilla.gnome.org/719966
|
|
|
|
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=749696
https://bugzilla.gnome.org/show_bug.cgi?id=751978
|
|
|
|
|
|
| |
Cases where fixed-size has no value and fixed-size has
a non-integer value where not yet tested. Found thanks
to coverage.py
|
|
|
|
|
| |
we already go through 'env' for all other TESTS_ENVIRONMENT
statements, reason to not do so here too...
|
|
|
|
|
| |
"--warn-all --reparse-validate" is already contained in
$(INTROSPECTION_SCANNER_ARGS), no need to repeat
|
|
|
|
|
|
| |
02e545371e2132a97458888895cacf57b8c0f83a (2015-06-23)
https://bugzilla.gnome.org/show_bug.cgi?id=725685
|
|
|
|
|
|
|
|
|
|
| |
"cairo-1.0.gir" is generated into "$(top_builddir)/gir" but
g-ir-scanner is never instructed to look into that directory.
This fails somewhat when there is no system installed copy
of it when VPATH building "tests/scanner/Regress-1.0.gir":
Couldn't find include cairo-1.0.gir (search path: "everything except the correct value")
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
42bb69a6a2f12165a9758b192e80da089e00ab5c introduced a bug causing
test_parser.py and test_patterns.py tests to be executed twice.
This patch fixes this and still allows the tests to be executed:
- using 'make check'
- manually:
PYTHONPATH=. python tests/scanner/annotationparser/test_parser.py
PYTHONPATH=. python tests/scanner/annotationparser/test_patterns.py
- individually:
python -m unittest test_parser.TestGiTag_Stability.test_001
python -m unittest test_patterns.TestCommentAsterisk.test_000
test_parser.py now results in:
Ran 360 tests in 0.172s
instead of:
Ran 720 tests in 0.339s
test_patterns.py now results in:
Ran 213 tests in 0.014s
instead of
Ran 426 tests in 0.041s
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
| |
libfoo was moved into libregress in 9fc6eb16e954559d97cdd9a03437c8b1877c2a1d
libtestinherit was moved into libregress in bb1ac9cf2dc450c5d44b1e39e3162ba06069f4a1
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
|
|
|
| |
tests/scanner/annotationparser/test_[parser|patterns].py
stopped working with Python3 somewhere down the line due
to the iteritems() call...
https://bugzilla.gnome.org/show_bug.cgi?id=745636
|
|
|
|
|
| |
Add missing doc-tool tests, fixes "make distcheck" breakage
introduced by 09daa28c5b4625b6f274b3b340bc85e33bef80b5
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751150
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750286
|
|
|
|
|
|
|
|
|
|
| |
Add the command line flag --symbol-filter-cmd to g-ir-scanner
which allows running symbol names through a filtering shell
command. The symbol is sent as stdin to the filter command
and expects a filtered result written to stdout.
https://bugzilla.gnome.org/show_bug.cgi?id=744534
Signed-off-by: Garrett Regier <garrett.regier@riftio.com>
|
|
|
|
|
|
|
| |
Allow `identifier`, `parameter` and `tag` part `annotations` fields
to span multiple lines
https://bugzilla.gnome.org/show_bug.cgi?id=676133
|
|
|
|
|
|
| |
Extends commit 92d9c38 to also pass CC to g-ir-scanner.
https://bugzilla.gnome.org/show_bug.cgi?id=700066
|
|
|
|
|
|
|
|
|
|
| |
Doing so reveals GIRParser did not yet support:
- the (skip) annotation on parameters and return values
- the (attributes) annotation
This patch fixes both issues an prevents further similar problems.
https://bugzilla.gnome.org/show_bug.cgi?id=738171
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What we already had:
- (array zero-terminated=1) > array which is NULL terminated
- (array zero-terminated=0) > array which is not NULL terminated
- (array) > array which is not NULL terminated
- (array zero-terminated=X) > array which is not NULL terminated
where X can be anything
What this patch adds:
- (array zero-terminated) > array which is NULL terminated
https://bugzilla.gnome.org/show_bug.cgi?id=657754
|
|
|
|
|
|
|
| |
This is an installed file, so we can't assume that config.h
will be around.
https://bugzilla.gnome.org/show_bug.cgi?id=737275
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RegressIntSet and RegressIntset, aliases of one another, were causing
two documentation pages to be built by the documentation tests that
were named identically except for letter case.
On OSX and Windows, the most common filesystems are case-insensitive,
and those two files can't exist in the same directory on case-
insensitive filesystems. That caused the tests to fail. It also caused
problems when checking out the repository, because the expected
documentation set also contains those files.
This commit fixes the symptom (so that JHbuild will stop erroring out
on this module) but not the problem of generating a documentation set
for two identifiers which differ (perfectly legally) only by case.
https://bugzilla.gnome.org/show_bug.cgi?id=725264
|
|
|
|
|
|
|
|
|
| |
We have special code to look at (type GLib.List(utf8)), but (type
GLib.PtrArray(utf8)) didn't work.
This allows NetworkManager to annotate the ActiveConnections property.
https://bugzilla.gnome.org/show_bug.cgi?id=733879
|
|
|
|
|
|
|
|
|
|
| |
This updates the test headers and sources to decorate the symbols with the
macro that can be used to export the symbols, and include config.h first in
the c-sources so that the macro can be defined with the compiler directive
to export the symbols. Update the CFLAGS as well so that the header that
defines the export decoration macro can be found.
https://bugzilla.gnome.org/show_bug.cgi?id=732669
|
|
|
|
|
|
| |
Update based additional test added with commit e2b96aaa4
https://bugzilla.gnome.org/show_bug.cgi?id=702508
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=702508
|
|
|
|
|
|
|
|
|
|
|
| |
Knowing the ownership transfer for instance parameters is
necessary for correct memory management of functions which
"eat" their instance argument, such as g_dbus_method_invocation_return_*.
Parse this information from the gir file and store in the
typelib, and then provide new API on GICallableInfo to
retrieve this.
https://bugzilla.gnome.org/show_bug.cgi?id=729662
|
|
|
|
|
| |
Add missing identfilter.py to EXTRA_DIST and correct spelling of
Identfilter-1.0-expected.gir.
|
|
|
|
|
|
|
|
|
| |
Add the command line flag --identifier-filter-cmd to g-ir-scanner which
allows running identifier names through a filtering shell command. The
identifier is sent as stdin to the filter command and expects a filtered
result written to stdout.
https://bugzilla.gnome.org/show_bug.cgi?706898
|
|
|
|
|
| |
Now that Cancellable and AsyncReadyCallback are being correctly
recognised again, adjust the expected output of the Regress testcase.
|