Hi,
thinking to a quite elegant solution using metaclasses).
it should be done at the C level, and I think, it shouldn't be too
difficult once one knows, which properties to support to achieve this.
OK, I'll have a look at this ASAP, if you wis ;-)
sure, go ahead.
I have
> solved my issues with pythonscript.py .
I already have a fix for this issue, just wanted to let you know ...
Is it available on the CVS repository or somewhere else (I have not
checked yet) ?
well, yes there is an cws cws_src680_pyunofixes2, which is currently
based on a quite SRC680_m106, where several fixes for pyuno went into.
The relevant patch is the last difference in
http://udk.openoffice.org/source/browse/udk/pyuno/source/module/pyuno.cxx?r1=1.6&r2=1.6.12.1
, basically a get() must be replaced by a getAcquired() because of this
strange semantics, that PyList_SetItem steals a reference.
One remark. I am not sure the use of "smart-pyref" is really a helpful
tool. I think this brings more confusion than help in the code. I have
no time to develop this now, but I can do it later if you think I am wrong.
I agree that this is not the common way how python C code is developed.
However in a world with c++ exceptions it becomes really very tedious to
do the refcounting by hand because want would have to introduce a lot
of additional try{} catch{} clauses to do the recounting right.
You need to concentrate on doing the smart-pyref right, when it is
constructed, but when you achieve this, it is very easy to add more
exits to a function without going through all the refcounting again.
Bye,
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
