Neels Hofmeyr c36e61e3dc 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		2018-08-20 12:41:36 +02:00
..
osmocom	use __FILE__, not __BASE_FILE__	2018-08-20 12:41:36 +02:00
Makefile.am	rename include/openbsc to include/osmocom/msc	2017-09-06 16:41:25 +02:00