> Are you *sure* Suggesting a complex workaround using #defines is worse than just having them do the right thing in the first place. And I suspect people would get confused and try "extern volatile struct foo f;" which won't work.