Re: Merging files to one

2013-11-14 Thread Eike Rathke
Hi, On Wednesday, 2013-11-13 10:17:04 +0100, Stephan Bergmann wrote: > However, a class whose implementation requires multiple thousand > lines of code is likely asking for some refactoring into more > manageable pieces anyway. It would take a real hero to refactor EditEngine, and with super cow

Re: Merging files to one

2013-11-13 Thread Stephan Bergmann
On 11/13/2013 09:34 AM, Tor Lillqvist wrote: But the main thing that speaks against re-combining source code files that clearly "belongs" together into one source file is the loss of (easy) access to version history. "git-blame -C" can make that a little less painful. And it's always debatabl

Re: Merging files to one

2013-11-13 Thread Tor Lillqvist
The number of source code lines in a .cxx file is as such not that relevant a factor determining resources consumed when compiling a source file. After all, the number of source lines *included* from headers during the compilation can easily be much more. The complexity of the code (especially so-c

Re: Merging files to one

2013-11-12 Thread Norbert Thiebaud
On Tue, Nov 12, 2013 at 8:52 PM, Jose Guilherme Vanz wrote: > Hi, All! > > These days when studying the source code to try solve the #43089 - > Syntax highlighting for Math. I found 5 source files with the same name > "impedit.cxx". Like this: > http://opengrok.libreoffice.org/search?q=impedit&pro

Merging files to one

2013-11-12 Thread Jose Guilherme Vanz
Hi, All! These days when studying the source code to try solve the #43089 - Syntax highlighting for Math. I found 5 source files with the same name "impedit.cxx". Like this: http://opengrok.libreoffice.org/search?q=impedit&project=core&defs=&refs=&path=&hist= Can we merge theses 5 files to just o