Skip to content

Latest commit

 

History

History
47 lines (29 loc) · 1.47 KB

Architecture.md

File metadata and controls

47 lines (29 loc) · 1.47 KB

A: 설계(Architectural) 아이디어

이 절은 보다 고수준의 구조와 라이브러리에 대한 아이디어를 포함한다.

구조적 아이디어 규칙 요약:

A.1: 코드의 덜 안정적인 부분에서 안정적인 부분을 분리하라

???

A.2: 잠재적으로 재사용 가능한 부분을 라이브러리로 표현하라

Reason
Note

A library is a collection of declarations and definitions maintained, documented, and shipped together. A library could be a set of headers (a "header only library") or a set of headers plus a set of object files. A library can be statically or dynamically linked into a program, or it may be #included

A.4: There should be no cycles among libraries

Reason
  • A cycle implies complication of the build process.
  • Cycles are hard to understand and may introduce indeterminism (unspecified behavior).
Note

A library can contain cyclic references in the definition of its components. For example:

???

However, a library should not depend on another that depends on it.