On 5/10/08, Alan McGovern [EMAIL PROTECTED] wrote:
1) Removed all unsafe code, everything is managed now
2) Improved performance of DoubleToInt64Bits and Int64BitsToDouble
pretty significantly, about 2.5x faster. I'd say this is mostly
because this implementation doesn't create an
Avery Pennarun wrote:
On 5/10/08, Alan McGovern [EMAIL PROTECTED] wrote:
1) Removed all unsafe code, everything is managed now
Is #1 really an advantage in the core library? Perhaps I've missed
some documentation here. It seems like these sorts of small, fast
functions are exactly what
On 5/12/08, Robert Jordan [EMAIL PROTECTED] wrote:
Side question: is there a sort of BitConverter that *always* returns
big-endian or little-endian, as requested? dbus-sharp (at least the
version I'm looking at) resorts to unsafe code to do this, which is
pretty gross. I see
Hi,
I did some work on BitConverter.cs which accomplishes the following:
1) Removed all unsafe code, everything is managed now
2) Improved performance of DoubleToInt64Bits and Int64BitsToDouble
pretty significantly, about 2.5x faster. I'd say this is mostly
because this implementation doesn't