That is still not "a YANG module that demonstrates the problem", just a fragment. But wrapping it into something that actually is a compileable module, which requires turning the type 'Name' into 'string' since there is no typedef for 'Name', and removing the 'must' expressions that references nodes that aren't included, I still don't see any actual problem. All the tailf:code-name statements generate corresponding #define's in the generated include file:
#define a_ip_pool_end_ip 1424737548
#define a_ip_pool_start_ip 1411652614
#define a_ip_pool_name 1998270519
Surely you don't expect #define's to be generated with literally 'ip-pool-end-ip' and the like, since that would just fail compilation - identifiers in C and most other programming languages cannot include the '-' character.
If you still think there is a problem, please provide a complete, compileable YANG module, and clearly state exactly what you consider to be a problem. Otherwise I have nothing further to add here.