.net - Why do the following differences in Silverlight implementations exist between MAC and Window versions -
i reading through list of differences between silverlight implementation windows , implementation mac. can found here.
while of differences related platform diffirences etc. there wonder why different @ all. if has thoughts or actual concrete information on this, interested hear input.
here few of things seemed strange, last point in list, prompted me post question.
- char.tolower(char, cultureinfo) - on mac current culture used rather specified culture. strange since mac presumably support multiple cultures (i don't own mac or know assumption on part)
- decimal/single/uint16/uint32/uint64 - document states mentioned types not supported, os not support them 'emulated' (i use term 'emulated' loosely since underlying cpu supports them excluding decimal of course).
- double/single *infinity properties - why have these return different strings on different platforms. not saying people should use string representation comparisons, silly, why make them different, isn't looking portability problems not need exist? or more platform specific user experience issue, mac users expect see infinity symbol rather words?
- cultureinfo constructor - on windows if invalid culture string passed constructor argumentexception thrown, on mac cultureinfo initialized current culture , no exception raised.
now none of these serious differences given code written according commonly understood best practices. however, wonder why thing consider, possibly incorrectly, part of behavior contract, though not explicit in .net, can expect when passing invalid culture string constructor, not deliver consistent behavior across platforms, seems rather arbitrary , again looking portability problems there there no reason, or there?
Comments
Post a Comment