From: Shriramana Sharma <samjnaa@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: Request help with function pointers
Date: Wed, 28 Feb 2007 21:02:49 +0530 [thread overview]
Message-ID: <45E5A0A1.8080607@gmail.com> (raw)
In-Reply-To: <200702270948.38776.kratzers@pa.net>
Stephen Kratzer wrote:
> Remove the space in ". *" and "-> *".
Thank you very much -- that worked, but is there any good reason why I
should not be allowed to put a space there? When I can use:
:: *
in the same programs without an error, why can't I use
. *
or
-> *
(I like having my code neatly and generously spaced since I feel it
looks cleaner.)
I get no problem if I space the . and -> in other cases like:
QWidget . show () ;
or
this -> show () ;
So if there is no good reason for not being allowed to put a space
between . and * or -> and *, I can report a bug against gcc asking for
this error to be removed for being meaningless.
Thank you.
Shriramana Sharma.
next prev parent reply other threads:[~2007-02-28 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 4:27 Request help with function pointers Shriramana Sharma
2007-02-27 14:48 ` Stephen Kratzer
2007-02-28 15:32 ` Shriramana Sharma [this message]
2007-03-07 16:49 ` Glynn Clements
2007-02-27 15:15 ` Stephen Kratzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E5A0A1.8080607@gmail.com \
--to=samjnaa@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.