You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Dennis E. Hamilton" <or...@apache.org> on 2016/03/01 17:30:57 UTC
[RISKS?] Dependability Issues with the AOO Code?
[BCC AOO PMC]
An interesting link came to my attention today:
<http://www.viva64.com/en/b/0308/>.
The analysis did not use the Apache OpenOffice code base. Because of common heritage from OpenOffice.org code, I expect most of the analysis to be applicable.
The conclusion might not be so favorable in our case, absent a systematic approach to AOO maintenance, especially around dependability problems.
-- Dennis E. Hamilton
orcmid@apache.org
dennis.hamilton@acm.org +1-206-779-9430
https://keybase.io/orcmid PGP F96E 89FF D456 628A
X.509 certs used and requested for signed e-mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RISKS?] Dependability Issues with the AOO Code?
Posted by Don Lewis <tr...@apache.org>.
On 1 Mar, Dennis E. Hamilton wrote:
> [BCC AOO PMC]
>
> An interesting link came to my attention today:
> <http://www.viva64.com/en/b/0308/>.
>
> The analysis did not use the Apache OpenOffice code base. Because of
> common heritage from OpenOffice.org code, I expect most of the
> analysis to be applicable.
>
> The conclusion might not be so favorable in our case, absent a
> systematic approach to AOO maintenance, especially around
> dependability problems.
Modern compilers warn about a lot of questionable code. Unfortunately
our build logs are currently so full of warnings from modern compilers,
I think it it easy for this signal to be obscured by the noise. That is
something that I'm interested in tackling.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org