Re: Two Tier, call_ str_ fix

Mukhsein Johari wrote:
> 
> I'm not sure what the problem is here :-(

Try this program:

!/usr/local/bin/prothon

print(Int)
print(Float)
print(String)

>...
> Maybe what we need is simply a change of syntax?
> 
> Instead of this:
> ob = MyObj()
> 
> To specify that ob is an object that inherits MyObj's
> attributes, why not:
> 
> ob = MyObj.inherit()

I proposed that new object instantation be separated from call_, but 
Mark Hahn said that they had already discussed it and decided against. I 
would still be in favour.

http://www.prothon.org/pipermail/prothon-user/2004-June/002339.html

>...  After all, prothon is protoype-based,
> right? Which means we don't use blueprint-like
> constructs like class.

In English the word "prototype" does in fact refer to something you use 
as a blueprint. "We've got a prototype of a velveeta-powered car and we 
hope to go into production next year." Similarly in Prothon, you almost 
always want hundreds of "instances" for each prototype.

Anyhow, I think that the "object" keyword was always just syntactic 
sugar for inherit+with.

  Paul Prescod