Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy do the following differences in Silverlight implementations exist between MAC and Window versions
    primarykey
    data
    text
    <p>I was reading the through the list of <a href="http://msdn.microsoft.com/en-us/library/cc838247%28VS.96%29.aspx" rel="noreferrer">differences</a> between the Silverlight implementation for Windows and the implementation for the MAC. Which can be found <a href="http://msdn.microsoft.com/en-us/library/cc838247%28VS.96%29.aspx" rel="noreferrer">HERE</a>.</p> <p>While some of the differences are obviously related to the platform diffirences etc. There are some that I just wonder why they would be different at all. If anyone has some thoughts or actual concrete information on this, I would be interested to hear your input.</p> <p>Here are a few of the things that seemed strange, especially the last point in my list, which is what actually prompted me to post this question.</p> <ol> <li><strong>Char.ToLower(Char, CultureInfo)</strong> - On the MAC the current culture is used rather than the specified culture. Strange since the MAC presumably does support multiple cultures (I don't own a MAC or know much about it so this is an assumption on my part)</li> <li><strong>Decimal/Single/UInt16/UInt32/UInt64</strong> - The document states that the mentioned types are not supported, is it that the OS does not support them so they are 'emulated' (I use the term 'emulated' loosely since the underlying CPU definitely supports them excluding Decimal of course).</li> <li><strong>Double/Single *Infinity properties</strong> - Why have these return different strings on the different platforms. Now I am not saying people should use the string representation for comparisons, that would be silly, but why make them different, isn't that just looking for portability problems where they do not need to exist? Or is this more a platform specific user experience issue, MAC users expect to see the infinity symbol rather than the words?</li> <li><strong>CultureInfo Constructor</strong> - On Windows if an invalid culture string is passed to the constructor an ArgumentException is thrown, on the MAC the CultureInfo is initialized as the current culture and no exception is raised.</li> </ol> <p>Now none of these are serious differences given that your code is written according to commonly understood best practices. However, I wonder why a thing I consider, possibly incorrectly, to be part of a behavior contract, though not explicit in .NET, like what I can expect when passing an invalid culture string to a constructor, does not deliver a consistent behavior across platforms, that seems rather arbitrary and again just looking for portability problems where there there is no good reason, or is there?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload