[pylucene-dev] JCC getter/setter bug?
janssen at parc.com
Wed Feb 20 15:12:19 PST 2008
I've now got a compile failing with the following:
build/_GoodStuff/__wrap__.cpp:1644: error: no 'void com::parc::support::FooBar::_set_m_b_atomic(jboolean) const' member function declared in class 'com::parc::support::FooBar'
Looking at the class with
$JAVA_HOME/bin/javap -classpath /tmp/x com.parc.support.FooBar
we find that it does indeed have something called "m_b_atomic":
public boolean m_b_atomic;
Looking at the JCC-generated FooBar.h file:
% grep m_b_atomic build/_GoodStuff/com/parc/support/FooBar.h
jboolean _get_m_b_atomic() const;
Sure enough, there's no "setter" for m_b_atomic generated.
I remember there was something like this in the gcj-PyLucene, wasn't
there? Some getter/setter issue?
More information about the pylucene-dev