nicholas clark suqhccl4org tue oct 23 2007 080640am 0400 andy dougherty wrote mon 22 oct 2007 jim cromie wrote hysterical raisins dont use static inline functions preference macros still portability issues would easier inline outline see effect yes historical memory serves inline wasnt viable option time would lot working code change amazingly difficult measure results changes difficult justify effort still good idea explore specifically iirc c99 standard chose different default linkage inline functions one gcc using think standards controlled addition keyword static believe wed need would inline functions truly inline additional linkable copy made also iirc severe limitations compiler must inline putting things like loops inside inline functions means compiler may choose inline plus cant guarantee compiler supports inline even used inline functions probably really could use replace current gcc brace group constructions although wouldnt bad achievement constructions obviate need least one global temporary scratch variable nicholas clark thu 07 aug 2008 001055 0100 inline code freeze