Re: linking c++ code with c library

On Jul 11, 5:07 pm, Paul N <gw7...@xxxxxxx> wrote:
On 11 July, 12:46, jacob navia <ja...@xxxxxxxxxx> wrote:





Nick Keighley wrote:

  ok, dynamic and static linking are not mentioned in the C standard..

Hence dynamic linking doesn't mean anything in the standard C
language. Implementations of C may implement these features.

This is just nonsense!

Linking is mentioned EXPLICITLY in the C Standard

See the C standard paragraph 5.1.1.2
"Translation phases".

Translation phase 8 (the final step) is
described as follows:

<quote>
All external object and function references are resolved. Library
components are linked to satisfy external references to functions and
objects not defined in the current translation. All such translator
output is collected into a program image which contains information
needed for execution in its execution environment
<end quote>

Linkers are further mentioned in an example, or referred to when
the identifiers contain wide characters.

Before spewing nonsense please READ the standard you are quoting.

I think he means that the C standard does not mention dynamic linking
or static linking (whatever they are). The draft standard only uses
the word "dynamic" a few times, none of which relate to linking, and
doesn't include the phrase "static linking".

The passage you've quoted doesn't use the words "dynamic" or "static"
or compare two different types of linking.- Hide quoted text -

- Show quoted text -

Thats fine. C Standard may not mention everytning about dynamic or
static linking. But, as a programmer, I believe everyone must know
about it. Every C programer uses library at one or other time. Just
because is is not mentioned in the standard, we should not escape such
things.
.

Relevant Pages

  • Re: linking c++ code with c library
    ... Linking is mentioned EXPLICITLY in the C Standard ... Translation phase 8 is ... Before spewing nonsense please READ the standard you are quoting. ...
    (comp.lang.c)
  • Re: linking c++ code with c library
    ... Linking is mentioned EXPLICITLY in the C Standard ... Translation phase 8 is ... Before spewing nonsense please READ the standard you are quoting. ...
    (comp.lang.c)
  • Re: #include vs. -library
    ... the C standard does not even require ... Linking is translation phase 8; ... While it does not require that they be external entities (whatever ...
    (comp.lang.c)
  • Re: #include vs. -library
    ... the C standard does not even require ... Linking is translation phase 8; ... While it does not require that they be external entities (whatever ...
    (comp.lang.c)
  • Re: Conversion from UTF32 to UTF8 for review
    ... interpretation of what the standard might have meant. ... name in its original language. ... An English translation of the Bible is at best a secondary ...
    (microsoft.public.vc.mfc)