What is good about Prothon?

[Greg Ewing]

has wrote:
> Not at all. I was arguing these issues long before Prothon got its
> copy() method.  I'm aware of its recent addition, but it doesn't
> really change anything: the canonical Prothon way to create new
> objects is still b = a(), not b = a.copy().

In that case you're not arguing about what the language
provides, but about the preferred style of using what the
language provides.

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg