public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: gcc@gcc.gnu.org
Subject: Re: (printf) ("hello world\n");
Date: Fri, 12 Dec 2003 13:07:00 -0000	[thread overview]
Message-ID: <20031212124807.GV29648@lug-owl.de> (raw)
In-Reply-To: <jmllpjxp8g.fsf@desire.geoffk.org>

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

On Thu, 2003-12-11 09:01:51 -0800, Geoff Keating <geoffk@geoffk.org>
wrote in message <jmllpjxp8g.fsf@desire.geoffk.org>:
> Segher Boessenkool <segher@kernel.crashing.org> writes:

> > That does not prevent you from declaring and defining your own
> > printf() function (with a different prototype) though; it only requires
> > that you make that function have external linkage.
> 
> You mean 'internal linkage'.  You can define your own function named
> printf only if you (a) do not include stdio.h and (b) declare it
> 'static'.

Um, I think:
	- You may include <stdio.h> as long as your new printf() has
	  compatible arguments. It's a Bad Thing, though, because
	  declaration in <stdio.h> doesn't really belong to your new
	  function.
	- You may also have your own function non-static. Then, it
	  depends on link-order which function (yours or libc's) is
	  used. Of course, that's horrible, too:)

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 --]

  parent reply	other threads:[~2003-12-12 12:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 20:41 Michael Elizabeth Chastain
2003-12-09 21:01 ` Dale Johannesen
2003-12-09 23:56 ` Geoff Keating
2003-12-10  9:53   ` Eyal Lebedinsky
2003-12-10 10:18     ` Andreas Schwab
2003-12-10 12:45       ` Robert Dewar
2003-12-10 13:12         ` Segher Boessenkool
2003-12-10 13:34           ` Robert Dewar
2003-12-10 13:36           ` Gabriel Dos Reis
2003-12-10 14:08           ` Joseph S. Myers
2003-12-10 14:17             ` Segher Boessenkool
2003-12-10 15:55               ` Andreas Schwab
2003-12-11 17:09               ` Geoff Keating
2003-12-11 17:39                 ` Segher Boessenkool
2003-12-12 13:07                 ` Jan-Benedict Glaw [this message]
2003-12-12 17:17                   ` Gabriel Dos Reis
2003-12-10 14:19             ` Register Spilling Umar Janjua
2003-12-11  7:59               ` Jim Wilson
2003-12-11  9:01                 ` Sanjiv Gupta

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=20031212124807.GV29648@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).