|
From: Nicholas N. <nj...@cs...> - 2008-12-03 06:08:06
|
On Tue, 2 Dec 2008, Robert Walsh wrote: > The Valgrind code is becoming dense with #ifdef's. As new > architecture and OS support is added, this is only likely to get > worse. I'm making this comment without any real thoughts on a good > (elegant and efficient) solution. Any ideas? Anyone else see this as > a problem, at least? AFAICT, for a lot of cases it's either #if/#ifdefs, or putting the arch/os/platform-specific code into a separate file. We currently use a mix of the two, #if/#ifdef for smaller things and separate files for bigger things. It's not great, but it is hard to see how else to do it. Nick |