Re: [boost] py_cpp review

From: David Abrahams (abrahams_at_[hidden])
Date: 2000-10-11 10:48:47

----- Original Message -----
From: "Gary Powell" <Gary.Powell_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, October 11, 2000 10:41 AM
Subject: RE: [boost] py_cpp review

> > I don't think there's a rigid official definition of the concept, but
does
> > it matter? After all, the function is just used to quickly filter out
> > names
> > we don't care about.
> >
> If that is the case, add one more char test that enforces
> "__?__" where "?" must be a non "_" non null character. All
> other forms won't match. The point of the complaint was that
> you weren't eliminating all of the bogus inputs before doing
> your search.

Python users are not supposed to touch names that begin and end with
double-underscores unless they are officially sanctioned special member
names. The Python documentation is (typically) vague in this area, but in
the community it is "well known Python lore" at least. The docs say:

The only non-bogus inputs are
> BTW. How come you added an optimization for early elimination, but are
> against an optimized search? Either it matters or it doesn't.
>
>   Yours,
>  -gary-
>
> > > file: subclass.cpp
> > >
> > >   Is "____" a special name? Because it appears that 4 underbar
> > characters
> > > would test true for this. I would have naively thought that at least
one
> > > more middle letter is required for a valid special name.
> > >

I always say "don't optimize prematurely" but in fact I don't always live by
that rule. If there is a simple