Amazon.com Widgets

When there is no good name...

I noticed a good debate going on the BCL blog (and now Krzysztof Cwalina’s blog) about the naming of TimeZone2…  Clearly the name brings back bad memories of the Win32\COM world …. As Krys points out there is not an easy answer here.  Ideally we could come up with a meaningful name, but lacking that, this seems like the least bad option…

Published 10 October 06 08:01 by BradA

Comments

# diegocanepa said on October 10, 2006 4:08 PM:

Hi Brad,

What about naming instead of TimeZone2 => TimeRegion

Regards

# Omer van Kloeten's .NET Zen said on October 10, 2006 4:21 PM:

Ever since Kathy Kam announced on her weblog that a new type named TimeZone2 will be introduced into

# Keith Patrick said on October 11, 2006 2:46 AM:

I noticed in the list of options, renaming the class was noticeably absent.  If the two classes are functionally different (and if one can't supersede the other because of breaking changes, then it isnt'), why not rename it?  MS already did it with ConfigurationSettings vs. ConfigurationManager, so the precedent is there.

On the positive side, it wasn't called TimeZoneEx.

# Judah said on October 11, 2006 11:37 PM:

TimeRegion sounds reasonable. Much preferrable to the COM-reminiscent TimeZone2 or TimeZoneEx

# gorshing said on October 16, 2006 12:16 PM:

I would rather see a new namespace for all these newer/extended classes.

New Comments to this post are disabled

Search

Go

This Blog

本博客中文版 (View in Chinese)



These postings are provided "AS IS" with no warranties, and confer no rights.

Syndication

Page view tracker