Primeiro Anterior Próximo Último         Casa


Common Code Patterns - Introduction - difficulties


Slide 3


Nota
The explanation of the sentences above:
- Moving the code to a core shared library - In some cases, the code is not project-specific (sometimes it is related only to few applications, and it's not a good idea to have this code in a core shared library, because it will unnecessary increase the size of these libraries).

- Moving it to a system library - sometimes the code is not huge enough pr generic enough to be moved to that kind of library. This happens with small specific functions (like a function to list the network intefaces, which is not kernel-level to be inserted in a system library, and may vary from one OS to another)

- Create a separated library for it - Since the function we are focusing on are small, split them into separate libraries doesn't seem to be a good idea, since it will increase the download and compilation time of excessive shared libraries

We should also remember the code that aren't plattaform specific. When this code is duplicated, the chance of keeping different implementations for the same task is increased, and in case of fixing the implementation, it's so difficult to get track of all different implementations

Criado em Dom 15 Ago 2004 por Gustavo P. Boiko and Helio C. de Castro com o KPresenter