Restructuring a giant, ancient codebase to make LibreOffice work well everywhere

Re:Restructuring a giant, ancient codebase to make LibreOffi... by gnachman on Thursday January 18, 2018 @06:47PM (#16182741)

I recall seeing a Google tech talk over ten years ago where they talked about cleaning up OpenOffice (or was it StarOffice?) it was memorable because they mentioned it did #define private public. I’m impressed they kept at it and it sounds like it’s going well. Still glad it’s not my project, though :)

[ Parent | on HN ]

Re:Restructuring a giant, ancient codebase to make LibreOffi... by the-tml on Friday January 19, 2018 @04:34AM (#16185076)

Sounded unfamiliar, so I checked. The Apache OpenOffice sources indeed have three such lines left (all in obscure fairly irrelevant parts of the code; two inside odd #ifdefs that are never true, one inside their OS/2 (yes!) backend). LibreOffice naturally hasn't any such crap any longer.

[ Parent | on HN ]

Re:Restructuring a giant, ancient codebase to make LibreOffi... by olavk on Friday January 19, 2018 @05:52AM (#16185338)

Do you know why both Apache OpenOffice and LibreOffice still exists?

[ Parent | on HN ]

Re:Restructuring a giant, ancient codebase to make LibreOffi... by chris_wot on Friday January 19, 2018 @07:11AM (#16185604)

History. Check the Wikipedia article.

[ Parent | on HN ]