One starting point is my last few patches, which involved a bug in one
of the string implementations, and buffer overflows.
On 3/1/2019 11:58 PM, Peter Kovacs wrote:
Do you have an example or can you explain how to find these. I'll have a
look.
On 02.03.19 04:31, Patricia Shanahan wrote:
The OpenOffice build system is both complicated and fragile. If you do
move things around, you MUST test the ability to build and install for
each supported OS.
To me, this change seems high risk for low benefit. I would far rather
see any available cycles put into replacing ad-hoc data structures
with STL structures.
On 3/1/2019 11:05 AM, Peter Kovacs wrote:
Hello all,
I am really annoyed by the Code. I see repentance and to me a code
concept is totally lacking.
What I would like to do is a general cleanup / refactoring pass.
I would like to start with similar features and move them together in
the same module, maybe even merge them.
As a process I suggest I post a mail with [refactor] in the subject. The
Mail will contain what will be moved merged, I collect all references in
the mail.
If there is no objection within 3+ days I conduct the move. (+ because I
need to find time to move and test the change.)
Is this a process feasible?
All the Best
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
