On Fri, Apr 22, 2011 at 10:11 AM, Steve Schveighoffer > In this case, it's not actually the library designer, but the user of the > library that is deciding the semantics. Big difference, and my huge problem > with D's properties. > > With strict properties, the power is to the library designer to decide on > semantics. With loose properties, it's to the user. You can think you are > creating a usable API, but it's still possible to abuse it. > > In other words, loose properties prevents *my* designs, even if it makes > *your* usage possible. Note that it's your usage, *not* your design that > you are enforcing. The API is beyond your control since the user is free to > call however he/she wants. > > So I think the language shouldn't hinder the library author's designs in > favor of the caller abusing usage. > > -Steve > > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos >
If you look at it this way, then I fail to see the problem with a little abuse. The library designer doesn't have to read the caller's code. Why should he/she care if the API is being abused a little?
_______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
