Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!paperboy!osf.org!dbrooks
From: dbrooks@osf.org (David Brooks)
Newsgroups: comp.lang.c
Subject: Re: low level optimization
Message-ID: <21227@paperboy.OSF.ORG>
Date: 19 Apr 91 19:12:46 GMT
References: <21660@lanl.gov> <1991Apr17.225944.15261@zoo.toronto.edu> <1991Apr18.190403.29049@Think.COM> <21846@lanl.gov> <1991Apr18.233807.19552@zoo.toronto.edu> <21868@lanl.gov>
Sender: news@OSF.ORG
Organization: Open Software Foundation
Lines: 30

In article <21868@lanl.gov>, jlg@cochiti.lanl.gov (Jim Giles) writes:
|> I see that I'm going to have to give a specific example.  Suppose
|> that functions A and B are in two separate files.  Suppose that
|> I compile them 'together' in some way (that is, the compiler makes
|> some use of internal knowledge of B while translating A and vice-versa).
|> Now, suppose I _change_ A and retranslate just A (I do _not_ retranslate
|> B).  The standard requires that I still be able to link both into a
|> single program.

This has never been the case.  Using pre-ANSI syntax:

B:

	some_routine(123);

A:

	some_routine(arg)
	int arg;
	{...

A after editing:

	some_routine(flag, arg)
	int flag, arg;
	{...
-- 
David Brooks				dbrooks@osf.org
Systems Engineering, OSF		uunet!osf.org!dbrooks
Donnie Wahlberg is brought to you by three billion years of evolution.