caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Problems linking in an object file produced with "ocamlopt -c -output-obj"
Date: Wed, 18 May 2005 10:02:30 +0200	[thread overview]
Message-ID: <871x85m06h.fsf@qrnik.zagroda> (raw)
In-Reply-To: <1116312743.32536.286.camel@pelican.wigram> (skaller@users.sourceforge.net's message of "17 May 2005 16:52:24 +1000")

skaller <skaller@users.sourceforge.net> writes:

> See ISO C99, 6.9.2./1
>
> Variables with external linkage must be defined exactly
> once (if they're used) or at most once (if they're not).
>
> The above fragments do not constitute an external definition,

They do. See 6.9.2/2.

-- 
   __("<         Marcin Kowalczyk
   \__/       qrczak@knm.org.pl
    ^^     http://qrnik.knm.org.pl/~qrczak/


      reply	other threads:[~2005-05-18  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 18:31 Corey O'Connor
2005-05-17  6:14 ` Corey O'Connor
2005-05-17  6:52   ` [Caml-list] " skaller
2005-05-18  8:02     ` Marcin 'Qrczak' Kowalczyk [this message]

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=871x85m06h.fsf@qrnik.zagroda \
    --to=qrczak@knm.org.pl \
    --cc=caml-list@inria.fr \
    /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).