From: dewar@gnat.com (Robert Dewar)
To: gcc@gcc.gnu.org, kth@srv.net
Subject: Re: c++ "with" keyword
Date: Sun, 05 Jan 2003 00:29:00 -0000 [thread overview]
Message-ID: <20030104233549.44473F29F3@nile.gnat.com> (raw)
> And to search for references to a structure becomes much more
> complex. Instead of looking for a '.x' or '->x', you must now search
> for 'x', and then look to see if the reference is within a 'using'
> clause.
You are imagining a very low level environment. In GNAT (using GPS) if you
click on an entity, you get immediately to its declaration, and of course
such a tool would disambiguate a reference immediately. You are also
talking about misuse of the feature if you are talking about hundreds of
lines of text.
> If long names are causing you typing problems, then DON'T CREATE LONG
> NAMES IN THE FIRST PLACE. The "standard" C and C++ libraries usually
> use fairly short names for everything. Most of the long names I've seen are
> those created specifically for the program in question. If the long
> names are
> a real problem for you, then why create them in the first place?
Well that's the strongest argument in *favor* of WITH so far :-)
Keeping names short because they are too painful to use is a significant
negative effect, since well chosen longish names can often make a big
difference to readability of code.
Now it is true that the C++ syntax style generally favors short names:
*p++
is a much nicer notation than
Julian_Date_At_Maturity++
so you could argue that a feature that made it more convenient to use long
names was inconsistent in style with C++ :-)
next reply other threads:[~2003-01-04 23:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 0:29 Robert Dewar [this message]
2003-01-05 0:37 ` Kevin Handy
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 13:07 Robert Dewar
2003-01-05 18:41 Robert Dewar
2003-01-05 13:03 Robert Dewar
2003-01-05 13:39 ` Toon Moene
2003-01-05 12:56 Robert Dewar
2003-01-06 12:18 ` Andrew Haley
2003-01-05 12:56 Robert Dewar
2003-01-05 18:22 ` Joseph S. Myers
2003-01-05 12:44 Robert Dewar
2003-01-05 3:16 Robert Dewar
2003-01-05 0:38 Robert Dewar
2003-01-04 23:27 Robert Dewar
2003-01-04 23:36 ` Lynn Winebarger
2003-01-05 2:55 ` Gianni Mariani
2003-01-04 22:13 Robert Dewar
2003-01-04 20:59 Robert Dewar
2003-01-04 22:36 ` Gianni Mariani
2003-01-04 20:09 Robert Dewar
2003-01-04 19:36 Robert Dewar
2003-01-04 19:59 ` Tolga Dalman
2003-01-04 19:13 Robert Dewar
2003-01-04 20:58 ` Gianni Mariani
2003-01-04 18:11 Robert Dewar
2003-01-04 18:47 ` Gianni Mariani
2003-01-04 17:52 Robert Dewar
2003-01-04 17:59 ` Gianni Mariani
2003-01-04 17:06 Robert Dewar
2003-01-04 17:22 ` Daniel Berlin
2003-01-05 11:33 ` Andrew Haley
2003-01-05 11:36 ` Toon Moene
2003-01-04 14:29 Robert Dewar
2003-01-04 15:00 ` Momchil Velikov
2003-01-04 15:24 ` Andrew Haley
2003-01-04 16:25 ` Neil Booth
2003-01-04 17:35 ` Gianni Mariani
2003-01-04 17:59 ` Tolga Dalman
2003-01-04 18:36 ` Gianni Mariani
2003-01-04 18:54 ` Tolga Dalman
2003-01-04 23:32 ` Kevin Handy
2002-12-29 8:32 Norman Jonas
2002-12-29 12:46 ` Russ Allbery
2002-12-29 6:49 Erik Schnetter
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=20030104233549.44473F29F3@nile.gnat.com \
--to=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=kth@srv.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).