Re: __FILE__ Without Full Path?
Re: __FILE__ Without Full Path?
- Subject: Re: __FILE__ Without Full Path?
- From: Steve Checkoway <email@hidden>
- Date: Thu, 29 Dec 2005 15:59:30 -0800
On Dec 29, 2005, at 2:33 PM, Nick Nallick wrote:
While I'm making a nuisance of myself, here's one for you kind
people...
I'm using the __FILE__ and __LINE__ constructs to log the origins
of runtime errors in my app. GCC is sending me the entire path to
the file, but I prefer just the file name (as CW provides). I'd
rather not embed the full path into released code if I don't have
to, plus there are a lot of these in my code and since the
executable size is up 50% over CW I'm looking for ways to trim it
down.
Gcc replaces uses the path to the file passed on the command line for
__FILE__. Xcode invokes gcc with an absolute path.
I've posted this before, but I think it's kinda neat.
Well, this is a bit of a hack, but if you include <string.h> you
can use this
#define THIS_FILE ((strrchr(__FILE__, '/') ?: __FILE__ - 1) + 1)
Is there some option I can give GCC or an alternate construct to
omit the path from the file name?
I wish.
- Steve
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden