[
https://issues.apache.org/jira/browse/PYLUCENE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064878#comment-16064878
]
Andi Vajda commented on PYLUCENE-37:
------------------------------------
If you use the wrappers generated for interfaces, you're going to face the
problem reported here.
If you use the wrappers generated for classes implementing said interfaces,
then you should be ok with all implemented methods anywhere as the implementing
class has them all (or it is abstract).
You can also force the wrapping of private classes by explicitly listing them
on the command line.
> Extended interfaces beyond first are ignored
> --------------------------------------------
>
> Key: PYLUCENE-37
> URL: https://issues.apache.org/jira/browse/PYLUCENE-37
> Project: PyLucene
> Issue Type: Bug
> Reporter: Jesper Mattsson
> Attachments: jcc.multiple.inheritance.patch, Test.zip
>
>
> When generating wrapper for a Java interface that extends more than one other
> interface, then only the first extended interface is used when generating the
> C++ class.
> In cpp.header(), the code snippets:
> {code}
> if cls.isInterface():
> if interfaces:
> superCls = interfaces.pop(0)
> {code}
> and:
> {code}
> line(out, indent, 'class %s%s : public %s {',
> _dll_export, cppname(names[-1]), absname(cppnames(superNames)))
> {code}
> are likely responsible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
