Re: why use -> (not .) with pointers?
- From: Clint Olsen <clint@xxxxxxxxx>
- Date: Thu, 30 Jun 2005 15:01:52 -0500
On 2005-06-30, Alan Balmer <albalmer@xxxxxxx> wrote:
> I think the OP was proposing that you could write structxp.fieldf even
> when structxp was a pointer to a struct. It's true that the compiler
> knows whether the dereference is required, but imo it doesn't fit with C
> philosophy (and don't ask me to define that ;-)
It's kind of interesting that the GNU debugger (gdb) has accepted the '.'
syntax for pointers to structs for as long as I can remember.
-Clint
.
- References:
- why use -> (not .) with pointers?
- From: Felix Kater
- Re: why use -> (not .) with pointers?
- From: jacob navia
- Re: why use -> (not .) with pointers?
- From: CBFalconer
- Re: why use -> (not .) with pointers?
- From: Alan Balmer
- why use -> (not .) with pointers?
- Prev by Date: Re: how to let gcc warn me when I use = in conditions
- Next by Date: Re: Implementing my own memcpy
- Previous by thread: Re: why use -> (not .) with pointers?
- Next by thread: Re: why use -> (not .) with pointers?
- Index(es):