On Thu, 2005-06-16 at 11:04 -0600, Peter Dennis Bartok wrote: > >Benchmarks really don't matter here I think. The *only* reason people > >would use the Locale class is when an exception gets thrown and we need > >to get the error message. Since an exception is 1) exceptional and 2) > >already slow, not too much harm in slowing it down more :-). > Ben, you are not correct. In MWF, the Locale class is used for getting > localized text for buttons in dialogs, for retrieving built-in images (for > dialogs), icons and cursors, and to retrieve the category and description > for viewing properties in propertygrid. Those are not in the main code path > and don't demand ultra-high speed, but performance does matter a bit
Ah, good point. Luckily, both code paths wouldn't be slow in MWF land (where speed is measured by the user, not a benchmark). Not to mention that the code only showed up in corlib. (it is in an ifdef). But it is good to keep that in mind. Anyways, I am sure that localization is going to incur some overhead for non-english cultures. For english, we should strive to make the overhead near 0. -- Ben _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
