CPPCON 2020 / CPPCON 2020 / MACRO-FREE TESTING MACRO-FREE TESTING WITH C++20 WITH C++20 | | | | HTTPS://BOOST-EXT.GITHUB.IO/UT/CPPCON-2020 HTTPS://BOOST-EXT.GITHUB.IO/UT/CPPCON-2020 KRIS@JUSIAK SINGLE (2K LOC) WITH NO EXTERNAL DEPENDENCIES (2K LOC) WITH NO EXTERNAL DEPENDENCIES MACRO-FREE (✔ ) MACRO-FREE (✔ ) (*) LIMITATIONS MAY APPLY (*) LIMITATIONS MAY APPLY HTTPS://GITHUB.COM/BOOST-EXT/UT SINGLE (2K LOC) WITH NO EXTERNAL DEPENDENCIES (2K LOC) WITH NO EXTERNAL DEPENDENCIES MACRO-FREE (✔ ) MACRO-FREE (✔ ) FEATURES ( FEATURES ( , , , , , , , , , , , , , , ) (*) LIMITATIONS MAY

give us a few pointers... 17Basic lab procedure: weighing a sample Question: do you believe we have 30 grams of coffee? Not 30g coffee! 18Basic lab procedure: weighing a sample Zero the scale with lab procedure: weighing a sample Only after calibrating our equipment for exactly the situation to be measured can we trust the result. Actually 30g of coffee 20This is exactly TDD's procedure for "The Scientific Method" 42Acknowledgements Kris Jusiak, Quantlab Financial Check out his C++20 macro-free unit test framework at github.com/boost-experimental/ut Neil Sexon, SciTec for peer reviews

程序设计，只在DOS 环境下 开发过软件，我在第１章为你安排了一些Win32 程序设计基础。这个基础至为重要，只 会在各个Wizards 上按来按去，却不懂所谓message loop 与window procedure 的人， 不可能搞定Windows 程序设计-- 不管你用的是MFC 或OWL 或Open Class Library，不管你用的是Visual C++ 或Borland C++ 或VisualAge DWORD time; POINT pt; } MSG; 8 接受并处理消息的主角就是窗口。每一个窗口都应该有一个函数负责处理消息，程序员 必须负责设计这个所谓的「窗口函数」（window procedure，或称为window function）。 如果窗口获得一个消息，这个窗口函数必须判断消息的类别，决定处理的方式。 以上就是Windows 程序设计最重要的观念。至于窗口的产生与显示，十分简单，有专 函数负责。稍后我们就会看到Windows 程序如何把这消息的取得、分派、处 理动作表现出来。 Mouse Driver Keyboard Driver System message queue Window Procedure Application message queue Messages from other windows USER Module Windows MYAPP.EXE SendMessage()

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference

.. set(CONAN_LIBS mylib ${CONAN_LIBS}) Those variables, will be used in the conan_basic_setup() macro to actually set the relevant cmake variables. If the developer wants to switch configuration of the ace/cmake/chat/src") set(PACKAGE_chat_BUILD "/examples/workspace/cmake/chat/build/Debug") macro(conan_workspace_subdirectories) add_subdirectory(${PACKAGE_say_SRC} ${PACKAGE_say_BUILD}) add_su because binary packages are not available). We can now proceed iteratively with the following procedure: 1. pop the first element of the first sublist of the build order result, get its ref reference