The Roles of Symmetry And Orthogonality In Design
unnecessarily complex • Weak Abstractions • Example: Component API is defined by external demands, not through internal cohesive purpose (such as: Adapter component) 2 Implementation Hygiene • Unnecessarily effects) • Achieved through: • Separation of Concerns • Encapsulation • Guarantees that modifying a component does not create nor propagate side effects to other components See: Edsger W. Dijkstra Separation interfaces A B Orthogonality grants simplicity to dismiss as a possibility some behaviors or component interactions within the resulting system.Charley Bay - charleyb123 at gmail dot com The Roles0 码力 | 151 页 | 3.20 MB | 5 月前3Better Code: Contracts
Rights Reserved. Innovation 1: Each component has a contract 1212 {x > 0, x < INT_MAX} y = x + 1 {y > 1}© 2023 Adobe. All Rights Reserved. Innovation 1: Each component has a contract 1212 {x > 0, x Rights Reserved. Innovation 1: Each component has a contract 1212 {x > 0, x < INT_MAX} y = x + 1 {y > 1}© 2023 Adobe. All Rights Reserved. Innovation 1: Each component has a contract 1212 {x > 0, x Rights Reserved. Innovation 1: Each component has a contract 13 13 {x < INT_MAX} y = x + 1 {y > 1}© 2023 Adobe. All Rights Reserved. Innovation 1: Each component has a contract 13 13 {x < INT_MAX}0 码力 | 204 页 | 4.46 MB | 5 月前3Conan 1.63 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 995 页 | 7.54 MB | 1 年前3Conan 1.62 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 993 页 | 7.53 MB | 1 年前3Conan 1.64 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 999 页 | 7.54 MB | 1 年前3Conan 1 Documentation
components["mycomponent"].set_property("cmake_target_name", �→"component_namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in␣ �→self.cpp_info (continues on next • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 975 页 | 8.75 MB | 1 年前3Conan 2.0 Documentation
using the components attribute of the CppInfo object to define the information for each separate component of a Conan package. Consumers can also select specific components to link against but not the rest such as algorithms, ai, rendering, and network. Both ai and rendering depend on the algorithms component. Please, first clone the sources to recreate this project. You can find them in the examples2 repository look at package_info() method in the conanfile.py and how we declared the information for each component that we want to provide to the consumers of the game-engine package: ... def package_info(self):0 码力 | 652 页 | 4.00 MB | 1 年前3Conan 1.57 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 971 页 | 7.69 MB | 1 年前3Conan 1.59 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 983 页 | 7.72 MB | 1 年前3Conan 1.58 Documentation
components["mycomponent"].set_property("cmake_target_name", "component_ ˓→namespace::mycomponent-name") # The property "cmake_build_modules" can't be declared in a component, do it in self. ˓→cpp_info self.cpp_info • cmake_build_modules property replaces the build_modules property. It can’t be declared in a component, do it in self.cpp_info. • cmake_find_mode will tell CMakeDeps to generate config files, modules the generator • component_version property supported by both generators that set a custom version to be used in the Version field belonging to the created *.pc file for that component. Properties related0 码力 | 979 页 | 7.71 MB | 1 年前3
共 112 条
- 1
- 2
- 3
- 4
- 5
- 6
- 12