On 6/25/07, Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx> wrote:
Using the preprocessor to create a project-specific language is seldom as good an idea as it may seem at the time, as you tend to end up with code which only the author understands. In general, to be able to work on a C source file should only require knowledge of C along with the types, variables and functions used by that particular file. Having to be familiar with a large number of project-specific conventions and idioms before you can touch anything tends to result in code which is hard to maintain.
Yes, now I agree. Well, if macros are not worse than __attribute__ declarations for machine-readability and if you acknowledge their usefulness, then maybe you should have given the reason above in the first place. ;-) Cheers, Pedro. - To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
