I think that "time2" is a good name, what it's supposed to mean "time2"? It's a time, just like that, but you can use *TimeSpan *in your model to handle the time. The actual implementation of "time" it's handled by a *DateTime*.
Another name to the type is: TimeAsTimeSpan (the opposite Oscar said, because it's not a TimeSpan handled by a Time, it's a Time handled by a TimeSpan). But this name it's too long I think. Working on this. On Thu, Mar 26, 2009 at 6:52 PM, Oskar Berggren <[email protected]>wrote: > I agree with option 2. Perhaps "TimeSpanAsTime"? > > /Oskar > > > 2009/3/26 Tuna Toksoz <[email protected]> > > +1 for 2nd >> >> Tuna Toksöz >> Eternal sunshine of the open source mind. >> >> http://devlicio.us/blogs/tuna_toksoz >> http://tunatoksoz.com >> http://twitter.com/tehlike >> >> >> >> >> >> On Thu, Mar 26, 2009 at 11:45 PM, Dario Quintana < >> [email protected]> wrote: >> >>> >>> 2) Or we can revert the "renaming" stuff. "TimeSpanInt64" to "TimeSpan", >>> and for the "TimeSpan" to another name, since "TimeSpan" lead to confusion. >> >> >> > -- Dario Quintana http://darioquintana.com.ar
