Share via


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…

Comments

  • Anonymous
    October 10, 2006
    Hi Brad, What about naming instead of TimeZone2 => TimeRegion Regards

  • Anonymous
    October 10, 2006
    Ever since Kathy Kam announced on her weblog that a new type named TimeZone2 will be introduced into

  • Anonymous
    October 10, 2006
    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.

  • Anonymous
    October 11, 2006
    TimeRegion sounds reasonable. Much preferrable to the COM-reminiscent TimeZone2 or TimeZoneEx

  • Anonymous
    October 16, 2006
    I would rather see a new namespace for all these newer/extended classes.