[Mono-dev] list of platform-differences

[Andreas Nahr]

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-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] Im Auftrag von Andreas
Heertsch
Gesendet: Dienstag, 22. September 2009 09:31
An: Andreas Nahr; mono-devel-list at 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 <ClassDevelopment at 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)

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20090922/04f98bbd/attachment-0001.html