Alex Rousskov wrote:
> On Fri, 2007-08-17 at 16:54 +1200, Amos Jeffries wrote:
>> I'm not sure its any worse than the macro definition itself.
>> .h is still bad though, any Ideas?
>
> You can replace the current comment with something like:
>
> /// To pool Foo objects, add MEMPROXY_CLASS(Foo) to the class Foo
> declaration
>
> Anybody who needs more hints can run "grep MEMPROXY_CLASS *.h" for
> numerous examples.
>
Hmm, good point. It is worth raising the intelligence bar on this one.
I've been thinking about that TODO also...
BUT on second thought is it more about merging the
MEMPROXY_CLASS_INLINE and MEMPROXY_CLASS into one class-internal macro??
Amos
Received on Sun Aug 19 2007 - 04:39:53 MDT
This archive was generated by hypermail pre-2.1.9 : Fri Aug 31 2007 - 12:00:05 MDT