diff options
| author | Rico Tzschichholz <ricotz@ubuntu.com> | 2017-07-20 10:47:26 +0200 |
|---|---|---|
| committer | Rico Tzschichholz <ricotz@ubuntu.com> | 2017-07-21 07:41:47 +0200 |
| commit | d48fb32d8350abbd421658c733b74aaf44cb89ce (patch) | |
| tree | 64a1f9f1b152881caab3bb1bce2c16eecf55a12a /tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page | |
| parent | 44aa990e80758ed9ad842fadc19857f26a663105 (diff) | |
| download | gobject-introspection-d48fb32d8350abbd421658c733b74aaf44cb89ce.tar.gz | |
regress: Test for property and method with conflicting names
This is something that libraries are not supposed to do, but some do
anyway (Soup and Clutter are two examples) and language bindings should
handle it somehow or other. In GJS we want to make sure that the way it's
handled doesn't change inadvertently, because buggy library code should
not break existing user code.
https://bugzilla.gnome.org/show_bug.cgi?id=785091
Diffstat (limited to 'tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page')
| -rw-r--r-- | tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page b/tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page new file mode 100644 index 00000000..a7945d12 --- /dev/null +++ b/tests/scanner/Regress-1.0-Python-expected/Regress.TestObj-name_conflict.page @@ -0,0 +1,14 @@ +<?xml version="1.0"?> +<page id="Regress.TestObj-name_conflict" + type="topic" + style="field" + xmlns="http://projectmallard.org/1.0/" + xmlns:api="http://projectmallard.org/experimental/api/" + xmlns:ui="http://projectmallard.org/1.0/ui/"> + <info> + <link xref="Regress.TestObj" group="field" type="guide"/> + </info> + <title>Regress.TestObj->name_conflict</title> + + +</page> |