openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: A refactoring proposal
Date Sun, 18 Jun 2017 08:19:15 GMT
In that case, we are talking about the same class. std::array is
defined in header <array>. See 
http://en.cppreference.com/w/cpp/container/array

On 6/17/2017 9:58 PM, Peter Kovacs wrote:
> The book says it is in <array>.
> The book is about C++11, providing a quick reference on C++.
> I cam across when I saw this youtube video: 
> https://www.youtube.com/watch?v=86xWVb4XIyE
> And since I learned C++ in the 90ies, but never used it I thought it is 
> a good invest.
> 
> Am 18.06.2017 um 01:06 schrieb Patricia Shanahan:
>> I don't know. I have not read that particular book. If the code
>> snippet includes "using namespace std" then "array" means "std::array".
>>
>> I have a time gap in my C++ experience - I used it professionally in the
>> 1980's, and now I'm coming back to it for AOO. I don't think the
>> Standard Template Library came into wide use until the 1990's.
>>
>> At this point I think we should use the STL for the next layer of data
>> structures above raw arrays, including arrays with bounds checking. I
>> have not heard of a competing library and I do not like to roll my own
>> if I can possibly avoid it.
>>
>>
>> On 6/17/2017 3:50 PM, Peter Kovacs wrote:
>>> +1
>>>
>>> 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
>>> Peter
>>>
>>> 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: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message