Timer::next conflicts with std::iterator::next


#1

using std::iterator::next() inside a class derived from juce::Timer yields a compiler error due to the Timer::next field. Simple namespace-wrapping doesn't work since it doesn't affect visibility inside a Timer-derived class. The clean solution would be to avoid name clashes with the STL.

Also, std::copy() and std::fill() are now recommended over memcpy() and memset(). Microsoft's Lavavej assures they shouldn't be any slower.

Cheers,

-- p


#2

Thanks for the heads-up - yep, I'll rename that.

And yup, if you're using the very latest compilers then std::copy and std::fill are the right functions to use. Sadly, a large chunk of the juce user-base aren't even on C++11 yet, so we have to keep things old-school :(