Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!spool.mu.edu!sol.ctr.columbia.edu!caen!uflorida!gatech!mcnc!decwrl!infopiz!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: Re: inline management (source included)
Keywords: inline, preprocessing
Message-ID: <3700@lupine.NCD.COM>
Date: 4 Feb 91 20:30:41 GMT
References: <1991Jan22.213115.8716@ctr@italy.eu.net>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 27

In article <1991Jan22.213115.8716@ctr@italy.eu.net> nicb@ctr.UUCP (Nicola Bernardini) writes:
>Is there anybody that has an evident solution to managing
>inline functions in a decent way?
>
>My problem is the following:
>
>1) I do not want to keep inlines in the definition files (.h)
>   because I want to be able to move my functions in and out
>   of inlining whenever I need to do so, without changing
>   header files to my clients.

See the other article I just posted.  It describes an automatic way of
getting .h files generated for you (by your makefile).

Using my scheme, it is easy to change a given inline routine into a
non-inline and vise-versa.  All you have to do is to move it below
the line in your .C file which acts as the delimiter between the
"implementation" and the "interface" part.

Note however that such actions may cause the .h file to change (automatically)
and that this in turn may cause a bunch of recompilations, but that's ok.

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.