All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "Linux-C-Programming (E-mail)" <linux-c-programming@vger.kernel.org>
Subject: Re: Stupid Question.
Date: Thu, 13 May 2004 16:38:52 +0200	[thread overview]
Message-ID: <20040513143852.GE1912@lug-owl.de> (raw)
In-Reply-To: <6.0.1.1.0.20040512125919.02e8cec0@no.incoming.mail>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

On Wed, 2004-05-12 13:02:25 -0600, Jeff Woods <Kazrak+kernel@cesmail.net>
wrote in message <6.0.1.1.0.20040512125919.02e8cec0@no.incoming.mail>:
> At 5/12/2004 02:53 PM -0400, John T. Williams wrote:
> >What does declaring a function static do?    ie
> >What is the difference between
> >static int blue() {
> >        return 0;
> >}
> >and
> >int blue() {
> >        return 0;
> >}
> 
> It makes the function visible only within the comilation unit it's in.  See 
> also:

A static function (or variable) will only be "visible" within exactly
that .c file which it is defined in.

Static automatic variables (those that are within functions) do have a
different semantic: their contents is preserved during multiple function
calls.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-13 14:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12 18:53 Stupid Question John T. Williams
2004-05-12 19:02 ` Jeff Woods
2004-05-13 14:38   ` Jan-Benedict Glaw [this message]
2004-05-13 18:27     ` Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2004-11-22  1:45 Stupid question Gene Heskett
2004-11-22  8:33 ` Jan Engelhardt
2004-11-22 12:21   ` Gene Heskett
2004-11-22 19:02     ` Jan Engelhardt
2004-11-22 19:21       ` Gene Heskett
2004-11-22 19:32         ` Jan Engelhardt
2004-11-23  2:11           ` Gene Heskett
2004-11-22 14:32 ` P
2004-11-22 15:58   ` Gene Heskett
2004-11-23 12:08     ` Nix
2004-11-23 12:19       ` P
2004-11-23 12:48         ` Gene Heskett
2004-11-23 12:46       ` Gene Heskett
2004-05-27  9:38 Marcel Hilzinger
2004-05-27  9:51 ` mjt
1999-08-18  6:39 Stupid Question Michael A. Thompson
1999-08-18  9:53 ` Martin Costabel

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=20040513143852.GE1912@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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.