linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alina Valea <avalea@home.ro>
To: linux-c-programming@vger.kernel.org
Subject: extern storage class & multiple declaration
Date: 22 Aug 2002 07:52:34 -0000	[thread overview]
Message-ID: <20020822075234.20104.qmail@relay1.home.ro> (raw)



Hello everybody,

Suppose we have:

---------------------------------------- file.h

extern int i; ----------------------------------------

and ---------------------------------------- file.c

#include "file.h"

int i; ...

/* No actual use of i here */
------------------------------------------

----------------------------------------- another_file.c

#include "file.h"

void func() {

i=3; }

-----------------------------------------

I know this is entirely correct, but is it an acceptable
programming habit?

Thank you, Alina


----

Home, no matter how far...
http://www.home.ro

             reply	other threads:[~2002-08-22  7:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22  7:52 Alina Valea [this message]
2002-08-22  8:02 ` extern storage class & multiple declaration Jan-Benedict Glaw

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=20020822075234.20104.qmail@relay1.home.ro \
    --to=avalea@home.ro \
    --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).