From: Gary Powell (Gary.Powell_at_[hidden])
Date: 2000-10-10 10:49:53
> Thanks for participating!
> > File : subclass.cpp
> > fn enable_special_methods(..)
> > the second for loop, has is_prefex(..., name + 2) done for each
> > of the loop, this should be done once outside the loop after the test
> > "!is_special_name(name)" While a good compiler should move this code,
> > not just do it since that's what you mean anyway.
> > same comment for enable_named_method
> One of us is completely nuts ;->. How can I move the test
> (is_prefix(enablers[i].name + 2, name + 2)) outside the loop if it depends
> on the loop index, i?
name += 2;
if (is_prefix(enablers[i].name + 2, name))
> > if BoundFunction returns a Ptr
> Nobody's calling the BoundFunction object; that's a ctor-initializer
> looking at.
> Naming details and boostification are still pending. Since the library
> itself has yet to get a final name (What's your vote?) it would be
> premature to select namespaces, I think.
> > If and when py_c++ becomes part of the standard, won't we have a
> > with the class names "String" and "Tuple" (I'm assuming that Jaakko
> > Tuple will also make the grade.)
> Not if they're properly namespace scoped ;->
I'm of the school that is planning on all boost libraries becoming part of
"std". I suppose that a c++ to python interface isn't as likely a candidate
as Tuple is for general inclusion but it would be nice to get the code names
so that it doesn't preclude it.
It one of those class names that is so overused to invite all future non
use. It's name has become almost meaningless unless there is some other bit
of information attached. That's why I favor PyPtrObject 'cause that's what
Why abbreviate this? Code is read 5 or 6 times for every time its
written. The few extra characters don't affect compile time or program
speed. It's part of my personal goal of write what you mean, name them what
Again these are my opinions and can be freely disregarded.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk