On 6/10/11 5:53 PM, bearophile wrote:
Lutger Blijdestijn:
Somebody one this newsgroup - maybe it was Don Clugston, also made a good
point against named parameters: it introduces inflexibility because now the
names of the parameters of a function become part of the public api.
Changing a name will now break client code.
Scala faces this problem:
http://www.digitalmars.com/d/archives/digitalmars/D/Deprecated_argument_names_131514.html
Bye,
bearophile
That's good evidence that introducing named parameters would be quite
involved.
Andrei
