Result of first test is First__CONCAT1(Second,Third), which is correct
behaviour of preprocessor , because "if an argument is stringified or
concatenated, the prescan does not occur".
But intuitively expected behaviour of __CONCAT() would be same as result of
second test - FirstSecondThird.
Please, could you allow chaining of __CONCAT() via atached patch ?
Summary: limited functionality of macro __CONCAT()
AssignedTo: drepper at redhat dot com
ReportedBy: Petr dot Salinger at seznam dot cz
CC: glibc-bugs at sources dot redhat dot com