Re: Re: "proto" versus "newObject"

From: "Paul Prescod"

> > We used up a lot of messages deciding between Proto() and Proto.new()
> > about a month ago here on the list.  At that time the concern was about
> > using up the call_ so it wouldn't be available for other purposes, which
> > I guess is just another way of saying that the namespaces overlap.  I
> > argued for keeping the Python way and won.  The problem is that the
> > "Proto()" construction technique is so fundamental to Python and it is
> > not "broken".
>
> It is not entirely broken but it also is not entirely explicit!
>
> And it may be causing a lot of these problems. I really didn't care much
> about the namespace of the prototype until I saw what was happening with
> call_ and str_.

This may be up for discussion again since the class proposal is up for
grabs.