Andreas and all
offcourse this could be expected - if I RFM (read the fucking manual). But
as a unexperienced mono user I expect, that mono sheelds me from
*any*hardware dependend issue.
I can understand, that this expectation is not fully realized in the
present, but I would not understand, that
Andreas Heertsch wrote:
Andreas and all
offcourse this could be expected - if I RFM (read the fucking manual). But
as a unexperienced mono user I expect, that mono sheelds me from
*any*hardware dependend issue.
I can understand, that this expectation is not fully realized in the
present,
@Robert
BitConverter is broken by design (by MS) and it can't be fixed.
Perhaps I'm too MS orientated, but as far as I understand, Mono starts to
make the .Net technology available for other platforms. So I think there
should be a wrapper around BitConverter (and simular functions), which
So I think there should be a wrapper around BitConverter (and simular
functions), which simulates a little endian system.
That sounds nice, but you should take it up with Microsoft. They already
do deploy .NET on big-endian systems (Xbox 360). Moving applications
between platforms is fairly
; mono-devel-list@lists.ximian.com
Betreff: Re: [Mono-dev] list of platform-differences
Andreas and all
offcourse this could be expected - if I RFM (read the fucking manual). But
as a unexperienced mono user I expect, that mono sheelds me from any
hardware dependend issue.
I can understand
Hi,
Well the BitConverter documentation says that it operates on the raw
bitstream, so this should be expected. Other than that afaik only the Buffer
class works directly on raw data. And of course anything related to
pointers will be endian-dependent as well.
Greetings
Andreas (other
