This is a multi-part message in MIME format. ------ extPart_000_000C_01C0DD99.D60EC1C0 Content-Type: text/plain; charset so-8859-1" Content-Transfer-Encoding: quoted-printable matz wrote: > You don't have to. But it might change Ruby's nature. It might no > longer be Ruby, but Ruby-masked Sather, maybe. I was afraid of this answer. I think, I was unclear: I don't wish any of the features of Sather. I am completely content with the current features of Ruby. The only thing I would like to achieve is a Ruby which produces faster code than Sather :) (of course, this is impossible, but sometimes an impossible objective is a good objective.) I think, Ruby in its current state has everything that a language needs to programm comfortably. The only thing it could need is: performance. My propositions were aimed at enabling the possibility of the programmer to optimize the performance locally without leaving the language. I think the proposed mechanisms are quite surficial and fit into the language smoothly both phylosophically, both because they don't violate backwards-compatibility and since they are optional. They would not make Ruby to a statically typed language or make a principially compiled language. They would jut open the possibility for compilers to optimize the code locally provided the programmer has given some hints. ------ extPart_000_000C_01C0DD99.D60EC1C0 Content-Type: text/html; charset so-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2614.3500" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>matz wrote:</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>> You don't have to. But it might change Ruby's nature. It might no<BR>> longer be Ruby, but Ruby-masked Sather, maybe.</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>I was afraid of this answer</FONT><FONT face=Arial size=2>. </FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>I think, I was unclear: I don't wish any of </FONT><FONT face=Arial size=2>the features of Sather.</FONT></DIV> <DIV><FONT face=Arial size=2>I am completely content with the current </FONT><FONT face=Arial size=2>features of Ruby. The</FONT></DIV> <DIV><FONT face=Arial size=2>only thing I would like to achieve is a Ruby </FONT><FONT face=Arial size=2>which produces faster</FONT></DIV> <DIV><FONT face=Arial size=2>code than Sather :) (of course, this is impossible, but sometimes </FONT></DIV> <DIV><FONT face=Arial size=2>an impossible objective is a good objective.)</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>I think, Ruby in its current state has everything that a language needs</FONT></DIV> <DIV><FONT face=Arial size=2>to programm comfortably. The only thing it could need is:</FONT></DIV> <DIV><FONT face=Arial size=2>performance.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>My propositions were aimed at enabling the possibility of the </FONT></DIV> <DIV><FONT face=Arial size=2>programmer to optimize </FONT><FONT face=Arial size=2>the performance locally without leaving the </FONT></DIV> <DIV><FONT face=Arial size=2>language. I think the proposed mechanisms are quite surficial</FONT></DIV> <DIV><FONT face=Arial size=2>and fit into the language </FONT><FONT face=Arial size=2>smoothly both phylosophically,</FONT></DIV> <DIV><FONT face=Arial size=2>both because they don't violate </FONT><FONT face=Arial size=2>backwards-compatibility and</FONT></DIV> <DIV><FONT face=Arial size=2>since they are optional.</FONT></DIV> <DIV><FONT face=Arial size=2>They would not make Ruby to a statically typed language or</FONT></DIV> <DIV><FONT face=Arial size=2>make a principially compiled language. They would jut open the</FONT></DIV> <DIV><FONT face=Arial size=2>possibility for compilers to optimize the code locally provided</FONT></DIV> <DIV><FONT face=Arial size=2>the programmer has given some hints.</FONT></DIV> <DIV><FONT face=Arial> </DIV></FONT></BODY></HTML> ------ extPart_000_000C_01C0DD99.D60EC1C0--