Then give them both options. You can still do this with strict properties, you
just have to name the functions something different.
-Steve
>________________________________
>From: David Simcha <[email protected]>
>To: Discuss the phobos library for D <[email protected]>
>Sent: Friday, April 22, 2011 4:35 PM
>Subject: Re: [phobos] Time to get ready for the next release
>
>
>
>
>
>On Fri, Apr 22, 2011 at 4:28 PM, Steve Schveighoffer <[email protected]>
>wrote:
>
>Unlike your example, writeln = "hello" is actually valid, correct code. That
>is, it's not utterly stupid, it's just utterly ugly (to you and me). If
>someone wants to call writeln that way because they like the "style", then
>that's their choice. I see no difference from what you propose.
>>
>>
>>
>>It's not about the compiler rejecting terrible code because it thinks the
>>code is terrible, it's about the compiler rejecting terrible code because the
>>library author thinks it's terrible. That is, the library author can decide
>>how you should use their code, just like he decides which functions are
>>private and public.
>>
>Right, but I don't want the power to control this. I don't want to be forced
>to decide such things for my users. I want my users to be able to do as they
>see fit.
>
>_______________________________________________
>phobos mailing list
>[email protected]
>http://lists.puremagic.com/mailman/listinfo/phobos
>
>
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
