__volatile__ __asm__

volatile is a C keyword, and programmers know better than using asm as an identifier. Why do people insist on using double underscores around them, especially Linux kernel developers?

Also, why do people use things like __attribute__((aligned(n))) instead of defining a macro ALIGNED(n)?

>>33
I already said what I had to say: Common Lisp is an ugly manbeast obviously designed by a committee, a very long time ago, and Scheme is underspecified (standard libraries?) and overcomplicated at times (macros anyone?). Both, as Lisps, share the same anti-feature that is Sexp-based syntax (with the aggravating factor that the language even encourages the proliferation of extra parentheses and deeper nesting levels), which results in code unreadability through lack of visual cues. I said it before and I'll say it again, stick a proper syntax on Lisp and you'll probably have something quite very decent, assuming the underlying Lisp isn't braindead (Lisp-1, delimited continuations, etc.) -- and yes, I know you can easily write a Lisp-1 interpreter in any Lisp-2, so don't bother arguing about the nature of the world `underlying'.

Uniformity is a great thing for macros (let's face it, it's the only feature that really needs them), and I believe you could still have macros equivalent in power with non-Sexp based syntax.

Will you fuck off and die now?