Re: why use -> (not .) with pointers?
- From: Guillaume <"grsNOSPAM at NOTTHATmail dot com">
- Date: Thu, 30 Jun 2005 18:17:19 +0200
lawrence.jones@xxxxxxx wrote:
Not anymore. But back in the dark ages, C was much less concerned about types than it is today and would allow pretty much *anything* as the left operand of . or ->. In that environment, the compiler couldn't figure out what to do, so having two different operators was essential.
To me, it's still essential syntactically speaking.
Letting the compiler "guess" what you mean is a really, really bad idea in general. Even when the case seems obvious to you. .
- Follow-Ups:
- Re: why use -> (not .) with pointers?
- From: Richard Tobin
- Re: why use -> (not .) with pointers?
- References:
- why use -> (not .) with pointers?
- From: Felix Kater
- Re: why use -> (not .) with pointers?
- From: lawrence . jones
- why use -> (not .) with pointers?
- Prev by Date: Re: Microsoft Visual C++ 6.0
- Next by Date: Re: why use -> (not .) with pointers?
- Previous by thread: Re: why use -> (not .) with pointers?
- Next by thread: Re: why use -> (not .) with pointers?
- Index(es):