A nice way to step into 2012

Timon Gehr timon.gehr at gmx.ch
Wed Dec 28 18:11:22 PST 2011


On 12/29/2011 02:02 AM, so wrote:
> On Thu, 29 Dec 2011 02:14:18 +0200, Timon Gehr <timon.gehr at gmx.ch> wrote:
>
>> On 12/29/2011 12:58 AM, so wrote:
>>> On Thu, 29 Dec 2011 01:48:57 +0200, Timon Gehr <timon.gehr at gmx.ch>
>>> wrote:
>>>
>>>> The moment NP by default is introduced is the moment all parameter
>>>> names in all libraries are set in stone.
>>>
>>> This is completely false. NP affects only those that "want" to use it,
>>> no one else. Again, no one.
>>> It is just like inline asm.
>>>
>>
>> No, it is not. If all parameters are named parameters, then the
>> library writers have to be aware of the fact that some users might use
>> named arguments. Again, every library writer is affected.
>
> Show me any library code from any language where library writer is not
> already "aware" their argument names define their function.
> They even document it that way.
>
> /// a does this, b does that
> void fun(int a, int b)

Documentation can be improved over time.
It cannot be argued that the widening of the set of exposed names is a 
positive aspect of named arguments.


More information about the Digitalmars-d mailing list