diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2018-08-20 12:41:36 +0200 |
---|---|---|
committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-08-20 12:41:36 +0200 |
commit | c36e61e3dc0212649e2560bfbd56a728dbefb24d (patch) | |
tree | 7401e8e8158632d5bdddf39b8094a992f7629c5e /tests | |
parent | 060a6c4d972b73a9e31f8d8bd13b67fd4d0b9a99 (diff) |
use __FILE__, not __BASE_FILE__
The intention was to use the file's basename, but __BASE_FILE__ means "the root
file that is being parsed and contains #include statements".
If we had a function using __BASE_FILE__ and that was defined in an #included
file, __BASE_FILE__ would indicate the first file where the #include is, and
not the file where the function is defined. __BASE_FILE__ works for us because
we don't ever include function definitions that log something, so __BASE_FILE__
always coincides with __FILE__ for our logging; but still __BASE_FILE__ is
semantically the wrong constant.
Related: OS#2740
Change-Id: I1c8122c909938daaf782468c1c5b0262d555c3ce
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions