Yes, I had the array activity in mind.
I am suggesting to do the same for pointers and references.
I am unsure which std methods are available in gcc version 4.1 or 4.4 however
we could maybe in case of smart and weak pointers fall back to boost if not
available in the compiler.
By this we can
I have suggested a refactoring pass to make more use of STL structures
instead of fixed size, unchecked arrays. Some security problem would be
caught by array bounds checking.
We have some new volunteers over on the recruitment mailing list. I
think refactoring would be a good project for gett
Good points!
But we need to address the dependency aging anyways.
Because modern system having difficulties with our code.
We must develop a plan how we modernise the code.
How about support by version:
With 4.x we will support whatever we have today.
5.x will be on newer compiler dependency.
M
On 14 Aug, To: dev@openoffice.apache.org wrote:
> On 14 Aug, Peter kovacs wrote:
>> Sorry, for my bad english.
>> I meant that I think that some of the functionality which we have
>> implemented in helper functions in the past can be retired by using
>> modern c++11 and later standards. The code wi
On 14 Aug, Peter kovacs wrote:
> Sorry, for my bad english.
> I meant that I think that some of the functionality which we have
> implemented in helper functions in the past can be retired by using
> modern c++11 and later standards. The code will be smaller,and
> according to Bjarne Stroustrup als
Sorry, for my bad english.
I meant that I think that some of the functionality which we have implemented
in helper functions in the past can be retired by using modern c++11 and later
standards.
The code will be smaller,and according to Bjarne Stroustrup also faster.
I also would like to limit if
Am 14.08.2017 um 19:38 schrieb Peter kovacs:
I am going through the code, when I have little time left.
:-)
There is a lot of code I think we don't need the modern implementation should
provide us similar functionality.
What do you mean with "modern implementation". Should newer libaries
Hello devs,
I am going through the code, when I have little time left.
There is a lot of code I think we don't need the modern implementation should
provide us similar functionality.
Is it okay if we target to get rid of such old Code?
Btw. There is a code for a workaround of a bug from gcc ve
