Make it possible to hide away parts of code in compiled snippets / symbol definitions about m.css

[marzer]

Oh, fun! I implemented pretty much exactly this in poxy without realizing you had this on the roadmap. Thought you might like a bit of an 'implementation experience' summary to serve as an example (or even just to see how it actually looks to help you make decisions re styling).

I went the magic macro route:

• Users put POXY_IMPLEMENTATION_DETAIL() in their code around features they want to hide
• Doxygen replaces that with just POXY_IMPLEMENTATION_DETAIL_IMPL (i.e. as if #define POXY_IMPLEMENTATION_DETAIL(...) POXY_IMPLEMENTATION_DETAIL_IMPL)
• Poxy's HTML post-process replaces all instances POXY_IMPLEMENTATION_DETAIL_IMPL with a C-style block comment /* ... */

Which looks like this: example

It'd be relatively simple to extend that approach to allow for user-defined macros and such. You'd obviously have much more power to do fun stuff here as part of the html generation step, rather than my kludgy post-process.

figure out a way how to make this builtin (provide a header with such definitions so the user can just #include <mcss.h>?

My relatively dumb way of solving this problem is to drag this snippet from project to project:

#if !defined(__POXY__) && !defined(POXY_IMPLEMENTATION_DETAIL)
	#define POXY_IMPLEMENTATION_DETAIL(...) __VA_ARGS__
#endif

Which doesn't require a separate header, of course, but is still invasive all the same. I guess the overhead is realtively low for any project with a single central preprocessor.h, or core.h or similar (which most will have), so either solution is going to be fine for most.