const, final, scope function parameters

Walter Bright newshound1 at digitalmars.com
Sat May 26 22:35:30 PDT 2007


It looks like making "const final scope" be the default for function 
parameters is going to be infeasible. The troubles are that:

1) It seems to knock a lot of people for a loop, who will be assuming 
that an undecorated name would be like an undecorated name for a local 
or global variable.

2) Having to turn off one of the const, final, or scope, introduces the 
need for some sort of "not" keyword, like mutable, !const, !final, etc. 
It comes off looking bizarre.

However, making "in" be equivalent to "const final scope" does seem to 
work fine, requires no new keywords, and doesn't seem to confuse anyone.

On a related note, "cstring" has received universal condemnation <g>, so 
   I'll just have to make "string" work.



More information about the Digitalmars-d mailing list