Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!udel!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Should I use macros to inline code?
Message-ID: <15601@smoke.brl.mil>
Date: 27 Mar 91 21:38:13 GMT
References: <1991Mar27.024602.21399@visix.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 18

In article <1991Mar27.024602.21399@visix.com> adam@visix.com writes:
>Given today's C compilers, is there any reason at all to explicitly
>inline code with macros?

Sure -- many of today's C compilers still don't inline functions.

>Assuming that's useful, is there any use for subroutines, so that a
>routine is only inlined once per function?

Rephrasing this to make sense, I guess you're asking whether if a function
is invoked only once there is any point to having it an actual function
rather than a macro (or in-lined).  The answer to that is, yes, it helps
immensely when using a typical debugger.

>(Actually, I don't see any way to pass arguments to and return from
>subroutines that would make them useful in C.)

???