Is everybody an idiot today??

[cjsmith]

For the C/C++ geeks out there, here's a grumpymaking thing I stumbled upon today.

In a .h file:

void __inline FUNCTION_NAME(mystruct* foo)
{
   foo->addrValid = TRUE; 
}

And therefore, in my .c file:

// HORRIBLE HACK!  Only one .o in an executable can have StupidInclude.h included.
// It defines inline functions and the link step will fail if multiple .o files
// contain those definitions.  But every .o in this type of executable must have the
// app data structure definition... which, for this app, relies on StupidInclude.h.
// Therefore, there can be only one .o in this executable.
#include "echoer.c"
#include "listener.c"
#include "pinger.c"

I know there are ways around this, potentially involving (say) precompiled headers, but this is supposedly a simple proof-of-concept app so I'm not bothering for now. And seriously. Who would release something like that and not get fired? Never mind; I know the answer.

Comments

[rfrench.livejournal.com]

Can you modify this .h file? If so, why not just make it a macro?

[cjsmith.livejournal.com]

Nope. That'd be the "right" solution, I think.