From owner-freebsd-questions Wed Aug 9 11: 8:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 2329A37BE87; Wed, 9 Aug 2000 11:08:37 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13MYUf-000DYg-00; Wed, 09 Aug 2000 17:14:13 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13MYUh-000ISg-00; Wed, 09 Aug 2000 17:14:15 +0100 Date: Wed, 9 Aug 2000 17:14:15 +0100 From: Ben Smithurst To: Ariel Burbaickij Cc: Mark Ovens , questions@freebsd.org Subject: Re: How to inhibit inline functions appearing during debugging(-g)fromshowing up ? Message-ID: <20000809171415.D48327@strontium.scientia.demon.co.uk> References: <20000809125157.B251@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ariel Burbaickij wrote: > I know that they are from ctype.h I also know the situations when these > functions are very handy , point is though I have neither included the > header nor typed the functions explicitly in by myself.So we are both > still searching for solution :) #define _DONT_USE_CTYPE_INLINE_ before your #include , and they should stop them. You should probably only use this when debugging though, since the inlines make the functions faster (as you might have guessed). ben@magnesium:~/tmp$ time ./countspaces