Re: Re: "proto" versus "newObject"

Mark Hahn wrote:

>...
> You don't have to do this if you don't want to.  If we get close to
> agreement on this I'll do it.  I'm starting to understand your proposal.  So
> far it seems like a lot of trouble to go to in order to keep the namepsaces
> seperate, which is not a problem I've ever worried about.

Let's propose just for argument's that the main problem is overlapping 
namespaces and the only two cases that matter are call_ and str_. In a 
recent message I suggested a "conventional workaround" for str_ that may 
be acceptable.

Here's my proposal for fixing call_: just say outright that prototypes 
are not derived from using call_. Use a new method called new() or 
"newObject()"

	File.new()
	List.new(someobj)

Is that too ugly?

	myfile = File.new("/tmp/foo.txt")

Another potential syntax is:

	myfile = new File("/tmp/foo.txt")

I think that obj.new() is quite explicit and readable about what is 
going on.

  Paul Prescod