On Fri, 13 Mar 2009 11:27:54 am R. David Murray wrote: > Seriously, though, the point is that IMO an application should not be > calling fsync unless it provides a way for that behavior to be > controlled by the user.
An admirable approach, but also a sweeping generalisation. Who is your expected user-base? Power users, who insist on being given the ability to configure every last aspect of the application behaviour? Or regular users who will be intimidated if you ask them to make the choice? Every configuration choice has a cost: not only does it require more effort to code and maintain, but it leads to a combinatorial explosion of test paths and greater opportunity for bugs. Why pay that cost if your application users won't consider the choice a feature? By all means give the user the option to make that choice, if they will consider it a feature. The point is that these are *application* decisions, not *language* decisions. Python shouldn't be making those decisions, but should be enabling application developers to make them. -- Steven D'Aprano _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
