Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site nsc-pdc.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!tektronix!reed!nsc-pdc!joemu
From: joemu@nsc-pdc.UUCP (Joe Mueller)
Newsgroups: net.lang.c
Subject: Re: Re: C programming hint
Message-ID: <464@nsc-pdc.UUCP>
Date: Fri, 19-Jul-85 12:55:18 EDT
Article-I.D.: nsc-pdc.464
Posted: Fri Jul 19 12:55:18 1985
Date-Received: Wed, 24-Jul-85 20:04:00 EDT
References: <899@teddy.UUCP> <729@asgb.UUCP> <730@asgb.UUCP> <257@harvard.ARPA>
Organization: NSC Portland Development Center, Portland Oregon
Lines: 20

> Anyone know of any efforts to standardize an indication to the compiler
> that it is or is not OK to compile standard library functions in-line?
> 
> Stew
> {seismo,ut-sally}!harvard!rubenstein

The committee discussed the question and decided that it should be done within
the realm of "# pragma" lines. This means that any compiler may offer this
feature but it will not be something that will be standardized. The # pragma
line was added to the standard to give implementors an easy way to turn
switches on or off in the compiler without adding new keywords. The line
could be something like:

# pragma inline	strncpy, sin, cos, absf

The # pragma directive is discussed in section C.8.5 of the draft. It doesn't
say much other than it causes implementation defined things to occur. By the
way, if anyone wants a copy of the draft, I believe it's now available for
informal public comment through CEBEMA for about $20. If there's enough
interrest, I'll try to find the address to send your money to.