Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!orion.cf.uci.edu!uci-ics!news
From: schmidt@zola.ics.uci.edu (Doug Schmidt)
Newsgroups: gnu.g++.bug
Subject: Re: static functions
Message-ID: <1989Sep10.003227.10906@paris.ics.uci.edu>
Date: 10 Sep 89 00:32:27 GMT
References: <8909092351.AA14187@sperm.ocean.washington.edu>
Sender: news@paris.ics.uci.edu (Network News)
Reply-To: schmidt@zola.ics.uci.edu (Doug Schmidt)
Distribution: gnu
Organization: University of California, Irvine - Dept of ICS
Lines: 26
In-reply-to: keffer@SPERM.OCEAN.WASHINGTON.EDU (Tom Keffer)

In article <8909092351.AA14187@sperm.ocean.washington.edu>, keffer@SPERM (Tom Keffer) writes:
>Michael,
>
>	This goes back to an earlier discussion we had as to whether
>-finline-functions should be the default.  
>

This reminds me...

Here's another relevant entry from the newly updated documentation from
g++.texinfo:

----------------------------------------
@item -fdefault-inline
If this option is enabled then member functions defined inside class
scope are compiled inline by default, @emph{i.e.,} you don't need to
add @var{inline} in front of the member function name.  If this option
is not enabled GNU C++ will not inline member functions by default.
----------------------------------------

Doug
--
schmidt@ics.uci.edu (ARPA) |   Per me si va nella citta' dolente.
office: (714) 856-4043     |   Per me si va nell'eterno dolore.
                           |   Per me si va tra la perduta gente.
                           |   Lasciate ogni speranza o voi ch'entrate.