[M3devel] operator overloading?

[Jay K]

"Obscures the underlying code" is true of so many things.
Exceptions. Garbage collection. Objects. Nested functions. Function calls! Default parameters. Generics. Pickles. RPC.
It is a matter of degree, cost, value though, granted.
  The runtime cost of operating overloading is zero, at least.
  And the unobscured code is horrible to read and write actually (which is the reason for many features).
  This is case where "obscure" is clearly good, and not obscure.
  But it is a matter of degree. I should probably try implementing it before I ask for it too strongly.


  - Jay

From: hosking at cs.purdue.edu
Date: Sun, 21 Nov 2010 13:33:31 -0500
To: jay.krell at cornell.edu
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] operator overloading?



Some of us find operator overloading anathema because it obscures the actual underlying code.It certainly does not fit well with the design philosophy of Modula-3.

On Nov 21, 2010, at 1:10 PM, Jay K wrote:Is it really so difficult to add operator overloading to the language?

>From a user's point of view, I know it is very useful in certain situations.


 - Jay





 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20101121/46277714/attachment-0002.html>