Re: bug in visual studio .net 2003 - breakpoints and memcpy

"Eugene Gershnik" <gershnik@xxxxxxxxxxx> wrote in message
news:uBtSIrwiFHA.1460@xxxxxxxxxxxxxxxxxxxxxxx

[...]

>> Indeed, why would anyone want to stick with a standard?
>
> Indeed why in this particular case?

And C++ compilers must also compile VB code, right?

> Well the standard is obviously out of sync with reality.

Out of sync with reality is somebody else. Your perception of reality breaks
down even on certain IA32 platforms, and the reality of the standard is far
more diverse.

> Googling on this issue reveals that even the standard comitteee members
> say so.

Looking at the standard is a much more straightforward way of listening to
the committee members.

[...]

> I still stand by what I wrote earlier. Either cast once and the cast will
> work or don't cast at all. The double cast doesn't buy anything here.

Converting between pointers and integers is useful and can be generally
implemented; converting between pointers-to-code and pointers-to-data is
also useful but cannot be generally implemented; this is all there is to it.

S


.

Relevant Pages

  • Re: to cast or not to cast malloc ?
    ... Nor did I ever promote casting malloc as general good C practice. ... descriptions as attacks on their beloved style rule (which they ... FWIW, I would advise most C programmers *not* to cast malloc calls, ... > actually existing standard, not some people's notion of what ...
    (comp.lang.c)
  • Re: unusual behaviour of program under linux....
    ... >> You don't need to do this cast. ... You need to stop casting the return value from malloc(). ... The ISO/ANSI C Standard says the some ways of arranging C code ... Undefined behavior is another one you will want to learn ...
    (comp.unix.programmer)
  • Re: call to malloc with size 0
    ... >> I've a simple qestion related to dynamic memory allocation in C here is ... Get rid of the cast. ... it just stops the compiler complaining about the problem. ... the appropriate standard header. ...
    (comp.lang.c)
  • Re: queries about sprintf
    ... >>> Can you make clear if you had something in mind about some special case or ... >>> some dark corner of the Standard this about, or if you simply dealt with the ... >> I hadn't even thought about that, I just perform the cast automatically ... >> and representation" are not sufficient to ensure interchangeability. ...
    (comp.std.c)
  • Re: Casting structure pointers
    ... > albeit it is not guaranteed by the standard. ... When a sockaddr_storage structure is cast as a sockaddr structure, ... ss_family field of the sockaddr_storage structure shall map onto the ...
    (comp.unix.programmer)
Loading