[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

9844: Re: [MUD-Dev] Naming and Directories?

[Full Header] [Plain Text]
From: Jo Dillon <emily@thelonious.new.ox.ac.uk>
Newsgroups: nu.kanga.list.mud-dev
Date: Thu, 18 Mar 1999 10:00:29 +0000
References: [1]
Organization: Kanga.Nu
Chris Gray (cg@ami-cg.GraySage.Edmonton.AB.CA) spake thusly:
> [Jo Dillon:]
> 
>  >  If it's that optimised might it not be defined in the header file,
>  >giving the compiler the source? I mean, if I was writing a highly
>  >optimised strcmp I wouldn't overlook the overhead involved in a function
>  >call...
[Elided]
> 'FD_SET', etc. Keep in mind that the practice of having short accessor
> routines be 'inline' is a C++ thing, and doesn't port to ANSI C (I think -
> I know gcc supports 'inline', but is it part of ANSI C?)

  Well, I was thinking a modern optimising C compiler might be smart enough
to inline without being told to do so with very short functions. This
might have changed since you last looked at the appropriate headers,
since after all compilers are getting more clever every year ;)
Also, in the specific case of includes designed to be used with gcc
(glibc?) 'inline' might well be used - after all C++ as well as C compilers
use the libc, and would benefit a lot from this sort of optimisation.

--
	Jo





_______________________________________________
MUD-Dev maillist  -  MUD-Dev@kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev