diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2018-08-20 12:40:43 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-08-20 12:40:43 +0200 |
| commit | c649c3fe8e3e8b1c2d04f75563be0f1837607f5c (patch) | |
| tree | 37d00c6b2ad9e9bb2f7dc32e083a684fcf0fa8c2 /include/osmocom/bsc/arfcn_range_encode.h | |
| parent | 4db98554fd23d1f6f5dcb46c7908ce42c95d979e (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: Ic6d9dafc96c9d467ae53be2cd41adcf26a4e5125
Diffstat (limited to 'include/osmocom/bsc/arfcn_range_encode.h')
0 files changed, 0 insertions, 0 deletions