Phil Thompson wrote:
> On Fri, 19 Feb 2010 11:24:40 +0100, Sébastien Petitdemange
> wrote:
>> Sébastien Petitdemange wrote:
>>> Phil Thompson wrote:
On Fri, 19 Feb 2010 10:42:51 +0100, Sébastien Petitdemange
wrote:
> Hi Phil,
>
> We use the latest sip (4.10) to wrap your C++
On Fri, 19 Feb 2010 11:24:40 +0100, Sébastien Petitdemange
wrote:
> Sébastien Petitdemange wrote:
>> Phil Thompson wrote:
>>> On Fri, 19 Feb 2010 10:42:51 +0100, Sébastien Petitdemange
>>> wrote:
Hi Phil,
We use the latest sip (4.10) to wrap your C++ library and I think I
foun
Sébastien Petitdemange wrote:
> Phil Thompson wrote:
>> On Fri, 19 Feb 2010 10:42:51 +0100, Sébastien Petitdemange
>> wrote:
>>> Hi Phil,
>>>
>>> We use the latest sip (4.10) to wrap your C++ library and I think I
>>> found a bug in the wrapping code generated by sip.
>>>
>>> Sip Code:
>>>
>>> cla
Phil Thompson wrote:
> On Fri, 19 Feb 2010 10:42:51 +0100, Sébastien Petitdemange
> wrote:
>> Hi Phil,
>>
>> We use the latest sip (4.10) to wrap your C++ library and I think I
>> found a bug in the wrapping code generated by sip.
>>
>> Sip Code:
>>
>> class HwSyncCtrlObj
>> {
>> %TypeHeaderCode
>
On Fri, 19 Feb 2010 10:42:51 +0100, Sébastien Petitdemange
wrote:
> Hi Phil,
>
> We use the latest sip (4.10) to wrap your C++ library and I think I
> found a bug in the wrapping code generated by sip.
>
> Sip Code:
>
> class HwSyncCtrlObj
> {
> %TypeHeaderCode
> #include
> using namespace lim
Hi Phil,
We use the latest sip (4.10) to wrap your C++ library and I think I
found a bug in the wrapping code generated by sip.
Sip Code:
class HwSyncCtrlObj
{
%TypeHeaderCode
#include
using namespace lima;
%End
public:
struct ValidRangesType
{
double min_exp_time;