linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darío Mariani" <mariani.dario@gmail.com>
To: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: various meanings of static
Date: Sat, 23 Jun 2007 09:55:16 -0300	[thread overview]
Message-ID: <84bd26ef0706230555x35fdceber20d5788370b602ee@mail.gmail.com> (raw)
In-Reply-To: <467CB8EC.8080209@gmail.com>

On 6/23/07, Shriramana Sharma <samjnaa@gmail.com> wrote:
> Hello.
>
> ...
>
> I am thinking of using # define-s to use these four words:
>
> local, sticky, classwide, nothis
>
> instead of static in my C++ programs to make them more meaningful. I
> believe that the above four are mutually distinct purposes of the single
> static keyword and whether a future C++ standard disambiguates these
> purposes or not (where I prefer it would) I can even now use these new
> clearer keywords.

IMHO, I think it's not a good idea to add your own keywords to your
code. This will make it harder for anyone else to read it.
Darío
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-06-23 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23  6:08 various meanings of static Shriramana Sharma
2007-06-23 12:55 ` Darío Mariani [this message]
2007-06-23 16:11   ` Glynn Clements
2007-06-24 21:08     ` Pedro de Medeiros
2007-06-25 21:35       ` Glynn Clements
2007-06-25 23:01         ` Pedro de Medeiros

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=84bd26ef0706230555x35fdceber20d5788370b602ee@mail.gmail.com \
    --to=mariani.dario@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 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 NNTP newsgroup(s).