"Brett Calcott" <brett.calcott@[...].nz>  writes:

> >
> > Wow, for some reason I couldn't see a generic solution and didn't
> > think of doing it that way.  That's totally cool!  Maybe I should
> > change the implementation in the library to allow non-const
> > PyTypeObjects.  It's more flexible, after all.
> >
> 
>  Yup - that makes sense. The only caveat is the requirement (at least with
>  VC6) to put a variable name in now:
> 
> > >  lvalue_from_nonconst_pytype<extract_identity<PyRectObject> >
> > >      need_this_or_msvc_barfs(&PyRect_Type);

I think making it into a function template would solve that ;-)

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


_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig