Re: pointer misunderstanding?

From: Alwyn (dt015a1979_at_mac.com.invalid)
Date: 11/11/04 

Date: Thu, 11 Nov 2004 13:58:32 +0000

In article <41932EE2.3346BB76@gascad.at>, Karl Heinz Buchegger
<kbuchegg@gascad.at> wrote:
>
> Your questions (in this and other threads) show that you
> have a very weak understanding of pointer basics.

I think, perhaps you are being a little harsh. C's pointer syntax is
somewhat counter-intuitive, and this can lead to mistakes even for
those who already understand 'the basics'. However, I believe your
suggestion of first practicing with specific types is an excellent one.

Alwyn

Relevant Pages

  • Re: WHILE Loop not exiting
    ... Karl Heinz Buchegger wrote: ... > The loop itself seems to be OK. ... The initial call to the function that contains this code is a pointer to the "head" of the ... Yes it is a tedious process but in the end ...
    (alt.comp.lang.learn.c-cpp)
  • Re: Smart pointer implementation
    ... Karl Heinz Buchegger wrote: ... >> Well, reference counting could, I suppose, give it to me, but I don't ... counted smart pointer for that task. ...
    (comp.lang.cpp)
  • Re: about cout output format
    ... >> Karl Heinz Buchegger ... 'something' is a pointer to characters, ... formatting function expects this to be a real 'string' (that is: ...
    (comp.lang.cpp)
  • Re: avoid polymorphism
    ... Karl Heinz Buchegger wrote: ... > If the compiler needs to compile a virtual function call he implements code ... > use the 'this' pointer of the object to locate the VTable. ... > If you need polymorphism, ...
    (comp.lang.cpp)
  • Re: VC6 Internal Error, My Fault?
    ... Karl Heinz Buchegger wrote: ... reference, ... and that a pointer or reference argument were the same ... I would get rid of all that memcpy(), ...
    (alt.comp.lang.learn.c-cpp)