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, that this expectation is not fully realized in the present, but I would not understand, that this would not be a challenge for mono. Andreas (this one) 2009/9/21 Andreas Nahr classdevelopm...@a-softtech.com 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 one) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] list of platform-differences
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, but I would not understand, that this would not be a challenge for mono. BitConverter is broken by design (by MS) and it can't be fixed. You can find a byte order aware converter in Mono's sources: http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/corlib/Mono/DataConverter.cs?view=co Feel free to include this file in your projects. Robert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] list of platform-differences
@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 simulates a little endian system. Then I don't have to take care of the underlaying platform, if I use BitConverter. Otherwise all people, who transport their apps to Mono and use such functions run in trouble (like me). Is that really necessary? Andreas ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] list of platform-differences
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 transparent unless you're depending on something platform specific, such as byte order. In that case you just have to be careful but your requirements are going to be fairly application specific. You could always use something like System.Net.IPAddress.NetworkToHostOrder -Thad ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] list of platform-differences
Sorry if I didn't make myself clear. I HAVE been talking about the MS documentation, not some mono specific one. This has nothing to do with Mono but is as specified by the MS .Net Framework. You will get the same issues with .Net Compact Framework if you don't have them already. These classes are designed especially for bit-level access (in fact I see little other use for them). mfg Andreas Von: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] Im Auftrag von Andreas Heertsch Gesendet: Dienstag, 22. September 2009 09:31 An: Andreas Nahr; 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, that this expectation is not fully realized in the present, but I would not understand, that this would not be a challenge for mono. Andreas (this one) 2009/9/21 Andreas Nahr classdevelopm...@a-softtech.com 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 one) ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] list of platform-differences
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 one) Von: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-boun...@lists.ximian.com] Im Auftrag von Andreas Heertsch Gesendet: Montag, 21. September 2009 17:51 An: mono-devel-list@lists.ximian.com Betreff: [Mono-dev] list of platform-differences As I became aware, that BitConverter.GetBytes(0x1234) returns 0,0 on OSX I thought: that is a bug. But Miguel pointed out, that this depends on the platform OSX: big-endian system (PowerPC) as opposed to a little endian system. Up to that I hoped, that mono would hide all differences of any plattform from my mono-app. But this seems not to be the case. (I think, this is a challenge!) Is there a list of platform specific differences, which have a reflection in mono? Andreas -- EndoTherm GmbH http://www.endotherm.ch ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
