VS2005 conversion of '\n\r' to 0x0D0A

Hello,

I'm not sure if it's VS2005 or its the other C compilers that don't adhere
to the C/C++ spec dealing with '\n\r', but to me, setting a word value
*((WORD*) ptr)='\n\r' is clear that it should be = 0x0A0D but VS2005
converts it to = 0x0D0A.

Just an FYI.



.

Relevant Pages

  • Re: VS2005 conversion of to 0x0D0A
    ... Can you please elaborate, from what is it clear what it should be? ...
    (microsoft.public.vc.language)
  • Re: How can I use a library?
    ... FASL format all Lisp compilers will adhere to. ... Lisp implementations based on the same ANSI standard. ...
    (comp.lang.lisp)
  • Re: C is too old? opinions?
    ... Comeau C/C++ (Unix and windows) ... The very fact that you need to list the implementations that support ... if you don't *know* what compilers may be used to compile ...
    (comp.lang.c)
  • Re: C is too old? opinions?
    ... jacob navia wrote: ... If your C *must* be 100% standard compatible amongst ALL compilers ... Comeau C/C++ ... You can generate lists of this kind for pretty much any ...
    (comp.lang.c)
  • Re: HLA v1.78 is now available
    ... > C really fits that niche too. ... > considering HLLs, doesn't it? ... Any examples of C/C++ compilers that produce commented assembly code? ...
    (alt.lang.asm)