[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-commits
Subject:    Re: [PATCH] D17741: adds __FILE_BASENAME__ builtin macro
From:       Nico Weber via cfe-commits <cfe-commits () lists ! llvm ! org>
Date:       2016-02-29 23:14:10
Message-ID: 0217c1609918b3b0e41d1d9ed7ae83a4 () localhost ! localdomain
[Download RAW message or body]

thakis added a subscriber: thakis.
thakis added a comment.

Instead of doing this, would it make sense to have a flag like -ffile-basename that \
changes what __FILE__ expands to?

I had wished I'd be able to have some control over __FILE__ (I'd like to say "make \
all __FILE__s relative to this given directory for my use case), and changing \
__FILE__ to something else in all the world's code isn't easy – so maybe having a \
flag that provides some control over __FILE__ instead of adding a separate macro \
would be a good idea.


http://reviews.llvm.org/D17741



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits


[prev in list] [next in list] [prev in thread] [next in thread]