> > Moving those #include out of the namespace{} and all seems
> > to compile just fine...
>
> Yep, that works.
Yes - not the tidiest looking change, but does the Right Thing.
> Congratulation, you're now a fltk3 developer! ;-)
Well, *technically*, I think I was anyway, as I changed a few minor
trivia the last time round too! ;-)
> But... why should all this thread stuff be in the fltk3 namespace
> at all? I *removed* all that fltk3 namespace stuff from threads.h,
> and here is my patch (some lines may wrap):
Yup - I thought about that, since this is only a test code, and
threads.h is not included anywhere else (well, not officially anyway,
though I sometimes use it in quick hacks...) then the namespace is not
really necessary.
But I thought it was maybe useful to show the "proper" thing in the test
code, so that was why I changed it the way that I did.
And it means that if I do pull in threads.h in some future test hack, I
don't have to worry about "polluting the global namespace" and all that
stuff...
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
