GOPHER CHINA 2020 中国 上海 / 2020-11.21-22 如何用go module构建模块化跨链平台 汪小益 趣链科技 ’ alt=‘OCR图片’/> 什么是区块链 跨链的重难点分析 跨链平台架构设计 Go module和plugin 的应用实践 GOPHER CHINA 2020 中国 上海 / 2020-11.21-22 1 什么是区块链 GOPHER alt=‘OCR图片’/> 中继链模块与流程 ’ alt=‘OCR图片’/> 为什么需要模块化 1 中继链和网关有大量公共组件 网络模块 执行模块 验证模块 协议处理模块 加密模块 2 灵活适配不同需求和版本 应用链访问模块 以太坊 Fabric 趣链区块链 天平链 共识模块 PBFT RAFT POS POA HOTSTUFF Golang提供了两种模块化工具，一个是go module，一个是go / 2020-11.21-22 4 GO module和plugin实践 GOPHER CHINA 2020 中国 上海 / 2020-11.21-22 4 GO modules实践：无处不在的模块 工具库（存储、加密、网络、日志等） https://github.com/meshplus/bitxhub-kit 验证引擎&IBTP协议库 https://github.com/meshplus/bitxhub-core

CMake # 现代 CMake 模块化项目管理指南 彭于斌 (@archibate) 课件 & 源码：https://github.com/parallel101/course 往期录播：https://space.bilibili.com/263032155 ## 第一章：文件 / 目录组织规范 基于 CMake 的 C/C++ 项目，如何优雅地、模块化地组织大量源文件？ ## 推荐的目录组织方式 目录组织格式： • 项目名 /include/ 项目名 / 模块名 .h • 项目名 /src/ 模块名 .cpp • CMakeLists.txt 中写： • target include directories(项目名 PUBLIC include) • 源码文件中写： • #include < 项目名 / 模块名 .h> • 项目名:: 函数名 (); ## 推荐的目录组织方式 推荐的目录组织方式 - 头文件（项目名 /include/ 项目名 / 模块名 .h）中写： • #pragma once • namespace 项目名 { • void 函数名(); • } • 实现文件（项目名 /src/ 模块名 .cpp）中写： • #include < 项目名 / 模块名 .h> • namespace 项目名 { • void 函数名 () {

access 394 36.9 Use naming conventions consistent with Julia base/395 36.10 Write functions with argument ordering similar to Julia Base 395 36.11 Don't overuse try-catch 396 36.12 Don't Don't expose unsafe operations at the interface level 397 36.18 Don't overload methods of base container types 397 36.19 Avoid type piracy 398 36.20 Be careful with type equality 398 36.21 Command-line Options 430 II Base 432 41 Essentials 433 41.1 Introduction 433 41.2 Getting Around 433 41.3 Keywords 437 41.4 Standard Modules 451 41.5 Base Submodules 452 41

. 430 36.9 Use naming conventions consistent with Julia base/ ..... 431 36.10 Write functions with argument ordering similar to Julia Base ..... 431 36.11 Don't overuse try-catch ..... 432 Don't expose unsafe operations at the interface level ..... 433 36.18 Don't overload methods of base container types ..... 433 36.19 Avoid type piracy ..... 434 36.20 Be careful with type equality switches for Julia ..... 470 II Base 472 41 Essentials 473 41.1 Introduction 473 41.2 Getting Around 473 41.3 Keywords 478 41.4 Standard Modules 493 41.5 Base Submodules 494 41.6 All Objects

. 430 36.9 Use naming conventions consistent with Julia base/ ..... 431 36.10 Write functions with argument ordering similar to Julia Base ..... 431 36.11 Don't overuse try-catch ..... 432 Don't expose unsafe operations at the interface level ..... 433 36.18 Don't overload methods of base container types ..... 433 36.19 Avoid type piracy ..... 434 36.20 Be careful with type equality switches for Julia ..... 470 II Base 472 41 Essentials 473 41.1 Introduction 473 41.2 Getting Around 473 41.3 Keywords 478 41.4 Standard Modules 493 41.5 Base Submodules 494 41.6 All Objects

. 447 36.9 Use naming conventions consistent with Julia base/ ..... 448 36.10 Write functions with argument ordering similar to Julia Base ..... 448 36.11 Don't overuse try-catch ..... 449 Don't expose unsafe operations at the interface level ..... 450 36.18 Don't overload methods of base container types ..... 450 36.19 Avoid type piracy ..... 451 36.20 Be careful with type equality switches for Julia 490 II Base 492 41 Essentials 493 41.1 Introduction 493 41.2 Getting Around 493 41.3 Keywords 498 41.4 Standard Modules 516 41.5 Base Submodules 517 41.6 All Objects

are the first line of defense (but not the only line) • Unit tests are an integral part of the code base ## Rule 0 ## Write unit tests ## DOMAINS Good Process Good Tests Good Code ## Part 1: Good Tests

. 447 36.9 Use naming conventions consistent with Julia base/ ..... 448 36.10 Write functions with argument ordering similar to Julia Base ..... 448 36.11 Don't overuse try-catch ..... 449 Don't expose unsafe operations at the interface level ..... 450 36.18 Don't overload methods of base container types ..... 450 36.19 Avoid type piracy ..... 451 36.20 Be careful with type equality switches for Julia 490 II Base 492 41 Essentials 493 41.1 Introduction 493 41.2 Getting Around 493 41.3 Keywords 498 41.4 Standard Modules 516 41.5 Base Submodules 517 41.6 All Objects

. 450 36.9 Use naming conventions consistent with Julia base/ ..... 451 36.10 Write functions with argument ordering similar to Julia Base ..... 451 36.11 Don't overuse try-catch ..... 452 Don't expose unsafe operations at the interface level ..... 453 36.18 Don't overload methods of base container types ..... 454 36.19 Avoid type piracy ..... 454 36.20 Be careful with type equality ... 493 II Base ..... 495 41 Essentials ..... 496 41.1 Introduction ..... 496 41.2 Getting Around ..... 496 41.3 Keywords ..... 501 41.4 Standard Modules ..... 520 41.5 Base Submodules .