openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Kovacs <>
Subject Re: A refactoring proposal
Date Sat, 17 Jun 2017 22:50:18 GMT

I have a question thought. In Tour of C++ (Bjarn Stroustrup) its 
recommended to use array instead of buildin arrays and only to use 
Arrays if we know the amount of elements (constexpr).

buildin arrays example:  Circle myarray[10]
array example: array<Circle,10> myarray

so std::array::at is equal to the arrayexample?
sorry if the question is dumb. I am not sure if what I know is the same 
what you talk about.
I am in the "early carrier" category. lol.

All the best

Am 17.06.2017 um 19:52 schrieb Patricia Shanahan:
> Without going into details here, some recently fixed security issues
> have related to the use of fixed size arrays without bounds checks.
> In general, that is not a very robust programming practice. It depends
> on careful checking in the source code to prevent array overflow.
> I suggest a project to replace raw arrays with Standard Template Library
> classes as appropriate. All accesses should be through safe functions
> such as std::array::at. In some cases we could replace a limited size
> but large array with e.g. a std::vector that can start small and grow
> only as needed.
> This matches nicely with my observations of volunteers. We are not
> getting many people with the skills and experience to dive into a
> very large body of code and debug it. We are getting students and
> early career programmers who could work on something like this. It
> might also be a viable Google Summer of Code project.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message