Re: How C compilers handle multiple function definitions.

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Tue, 30 Dec 2008 07:35:17 +0000 (UTC)

          From comp.compilers
Related articles
How C compilers handle multiple function definitions. typingcat@gmail.com (RealCat) (2008-12-28)
Re: How C compilers handle multiple function definitions. armelasselin@hotmail.com (Armel) (2008-12-29)
Re: How C compilers handle multiple function definitions. mburrel@uwo.ca (Mike Burrell) (2008-12-29)
Re: How C compilers handle multiple function definitions. gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-12-30)
Re: How C compilers handle multiple function definitions. kamalpr@hp.com (kamal) (2009-01-01)
Re: How C compilers handle multiple function definitions. kamalpr@hp.com (kamal) (2009-01-01)
| List of all articles for this month |
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Tue, 30 Dec 2008 07:35:17 +0000 (UTC)
Organization: California Institute of Technology, Pasadena
References: 08-12-107 08-12-108
Keywords: C, Fortran, comment
Posted-Date: 31 Dec 2008 11:06:34 EST

Armel <armelasselin@hotmail.com> wrote:
(snip)


> It seems that there is no real standard shared by all _linkers_ but
> the "one function per object" paradigm makes your question simple
> enough to be sure that the _first_ "function module" is considered the
> one to choose


For C that is fine, but for languages with an ENTRY statement,
such as Fortran and PL/I, it gets more complicated.


-- glen
[Same problem if you have a couple of C routines that share data with
file-level static data. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.