[
https://issues.apache.org/jira/browse/PYLUCENE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181996#comment-17181996
]
Andreas Vajda commented on PYLUCENE-55:
---------------------------------------
You ask:
> What is the reason for so different generated modules?
I don't know yet since I've not been able to reproduce the problem as reported.
> How the order of class wrapper generation influences the resulting methods?
The order of method generation should not matter.
> Why some methods sometimes are NON generated?
So far, all methods you told me about were generated in my build. I have not
been able to
reproduce the problem as reported yet. However, by default, only public methods
get wrappers.
It seems that all the methods in question so far are indeed public.
> JCC creates the classes in non-deterministic order
> --------------------------------------------------
>
> Key: PYLUCENE-55
> URL: https://issues.apache.org/jira/browse/PYLUCENE-55
> Project: PyLucene
> Issue Type: Bug
> Reporter: Andrea Sterbini
> Priority: Major
>
> I am trying to wrap the BabelNet API code.
> The resulting module is non-deterministically not-working (once every 5 I get
> it OK).
> This seems to be related to the order the classes are handled, because they
> are kept in a set, which has nondeterministic order.
> By changing cpp.py at line 696 to sort the class names I get a working module.
> {code:java}
> // changed from
> for cls in todo:
> {code}
> {code:java}
> // to
> for cls in sorted(todo, key=lambda c: c.getName()):{code}
> I have been luky with this way to order the classes. Possibly a better
> algorithm exists to fix this bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
