Basic question about Juce Arrays

[nicolasdanet]

The “std vs JUCE container” is a question that comes often (JUCE was there from before C++11 birth).

Juce classes vrs c++ std

TL;DR for this question: Yes, JUCE was written way back in the old days, when the standard containers were really unsatisfactory, and most libraries rolled their own container classes. Since C++11 became a thing, our advice is that if you can use the new standard, then you should prefer things like std::unique_ptr, std::vector, std::array, etc. The JUCE equivalent classes do their best given the contraints of c++98, and some people will probably always prefer them for various reasons, but the …

Shouldn't juce::Array::operator[] return a const?

I also agree. But the array class was one of the first classes that I wrote back in the last millenium, and I wasn’t quite such a C++ ninja back then. If I’d written it now, it’d certainly be very different, but to change it now would break a lot of dependant code. The mistake I made was in saying that it’s ok to call operator[] with an out-of-bounds array index, which means that it can’t return a reference, because for invalid indexes, it’ll need to return a new default object. In my own code,…