Dominique Devriese <[EMAIL PROTECTED]> writes:

> David Abrahams writes:
>
>>> Hi,
>>>
>>> I'm the main developer of Kig [1].  I have just committed the code
>>> for python scripting to the CVS repository
>
>> Using Boost.Python?  Cool!
>
> Yups, I was going to post something separately about including it on
> the "projects using boost.python" page if you want, but well, erm..
> if you want, feel free to include it on that page.. :)  ( There's no
> released version with the scripting yet, but I consider the code
> itself to be pretty stable.. )
> If you need more information, feel free to ask.

Please give me a blurb for the page, preferably in HTML, so I don't
have to work too hard.

>>> Are there any plans to release a fixed version of Boost.Python any
>>> time soon
>
>> No specific plans, no.
>
>>> and what is the policy on Boost.Python releases in general ?
>
>> In general, they are released when all of Boost is ready.  I think
>> it would be a *really* good idea for Boost to do at least one minor
>> version release shortly after any major version release.  Now that
>> we have a reasonable testing strategy it should be relatively easy.
>> Boost 1.30.0 went out with several bugs IIRC.
>
>> Until we get our act together, I would suggest you supply people
>> with a Boost patch.  Use "BOOST_DEDUCED_TYPENAME" instead of
>> "typename" so you don't break VC6.  Sorry,
>
> A fixed release would be great indeed.  In the mean time, I'm going to
> provide the patch as you suggest, although it's far from a perfect
> solution of course..

I know.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to