C++ in the CloudC++ in the Cloud One NIF at a Time with Elixir Sakshi Verma | Senior Software Engineerhttps://www.linkedin.com/in/sakverma Functional, concurrent language built for scalability. Ideal for managing managing large-scale cloud applications. Built on the Erlang VM, ensuring resilience and fault tolerance. What is Elixir?https://www.linkedin.com/in/sakverma The Smooth Sailing…https://www.linkedin0 码力 | 14 页 | 609.86 KB | 6 月前3
《深入浅出MFC》2/e祝您身体健康!! ix Chengwei chengwei@accton.com.tw 最近正拜读大作深入浅出MFC,明显感受到作者写书之负责用心(不论内容、排版设计、 甚至用字遣词乃至众多的图标)。虽然刚开始会觉得有些艰涩,但在反复阅读之后便能深深 感受其中奥秘。谢谢你的努力! 请再接再厉让我们有更多好书可看! Fox Wang身为您的忠 窗口类别(不是一种 C++ 类別) window focus 窗口焦点(拥有焦点之窗口,将可获得键盘输入) 以下是本书使用之中英文名词对照表: 控制组件,如 拖放(鼠标左键按下,选中图标后拖动,然后放开) 图标(窗口缩小化后的小图样) 串行 列表框、列表清单 通告消息(发生于控制组件) 强制性、先占式、优先权式 进程(一个执行起来的程序) 队列 template C++ 有所谓的class Windows 程序分为「程序代码」和「UI(User Interface)资源」两大部份,两部份最后以RC 编译器整合为一个完整的EXE 文件(图1-1)。所谓UI 资源是指功能菜单、对话框 外貌、程序图标、光标形状等等东西。这些UI 资源的实际内容(二进制代码)系借助各 种工具产生,并以各种扩展名存在,如.ico、.bmp、.cur 等等。程序员必须在一个所谓 的资源描述档(.rc)中描述它们。RC 0 码力 | 1009 页 | 11.08 MB | 1 年前3
Back to Basics: Debugging Techniquesnext = Clone(curr); while (ReproduceProblem(next) && ResourcesAvailableToRepair(next)) { auto insight = async(launch::async, &MyJob::UnderstandProblem, this, next); auto location = async(launch::async this, next); auto category = async(launch::async, &MyJob::ClassifyProblem, this, next); WaitFor(insight, location, category); next = AttemptToRepair(next); } return (ProblemFixed()) ? Deliver(next) next = Clone(curr); while (ReproduceProblem(next) && ResourcesAvailableToRepair(next)) { auto insight = async(launch::async, &MyJob::UnderstandProblem, this, next); auto location = async(launch::async0 码力 | 44 页 | 470.68 KB | 6 月前3
What Volatile Means (and Doesn't Mean)cv-qualifiers starts with understanding the structure of declarations… 29 The Structure of Declarations Insight: Every object and function declaration has two main parts: a sequence of one or more declaration []mean “array” ()mean “function” 31 Type vs. Non-type Specifiers Insight: Type specifiers modify other type specifiers. Insight: Non-type specifiers apply directly to the declarator-id. static unsigned (and Doesn't Mean) Copyright © 2024 by Ben Saks and Dan Saks 0-15 volatile is a Type-Specifier Insight: The order of the declaration specifiers doesn’t matter to the compiler. These two declarations0 码力 | 32 页 | 901.80 KB | 6 月前3
Hello 算法 1.1.0 C++ 版iongsp、nanlei、a16su、 cy‑by‑side、gaofer、malone6、Wonderdch、hongyun‑robot、XiaChuerwu、yd‑j、bluebean‑cloud、 iron‑irax、he‑weilai、Nigh、MolDuM、Phoenix0415、XC‑Zero、SamJin98、reeswell、NI‑SW、 Horbin‑Magician、x 纸质图书的两次印刷的间隔时间往往较久,内容更新非常不方便。 而在本开源书中,内容更迭的时间被缩短至数日甚至几个小时。 1. 内容微调 如图 16‑3 所示,每个页面的右上角都有“编辑图标”。您可以按照以下步骤修改文本或代码。 1. 点击“编辑图标”,如果遇到“需要 Fork 此仓库”的提示,请同意该操作。 2. 修改 Markdown 源文件内容,检查内容的正确性,并尽量保持排版格式的统一。 3. 在页面底0 码力 | 379 页 | 18.47 MB | 1 年前3
Hello 算法 1.2.0 简体中文 C++ 版sp、JeffersonHuang、Transmigration‑zhou、magentaqin、Wonderdch、 malone6、xiaomiusa87、gaofer、bluebean‑cloud、a16su、Shyam‑Chen、nanlei、hongyun‑robot、 Phoenix0415、MolDuM、Nigh、he‑weilai、junminhong、mgisr、iron‑i 纸质图书的两次印刷的间隔时间往往较久,内容更新非常不方便。 而在本开源书中,内容更迭的时间被缩短至数日甚至几个小时。 1. 内容微调 如图 16‑3 所示,每个页面的右上角都有“编辑图标”。您可以按照以下步骤修改文本或代码。 1. 点击“编辑图标”,如果遇到“需要 Fork 此仓库”的提示,请同意该操作。 2. 修改 Markdown 源文件内容,检查内容的正确性,并尽量保持排版格式的统一。 3. 在页面底部填写修改说明,然后点击“Propose0 码力 | 379 页 | 18.48 MB | 10 月前3
Performance Engineering: Being Friendly to Your Hardware} Let the HW do the right thing • Microcoded subroutine • Aware of platform specifics • Has insight into internal machine stateExample – memcpy: ERMS 92 0000000000001260 <_Z11memcpy_ermsPvPKvm>: } Let the HW do the right thing • Microcoded subroutine • Aware of platform specifics • Has insight into internal machine state Will this universally be the best option? Only representative performance0 码力 | 111 页 | 2.23 MB | 6 月前3
C++20 镶 SQLftsd::get<"item">(row) << " "; std::cout << get<"discount_code">(row).value_or("") << "\n"; }Key Design Insight u For types with SQL, you only need to worry about input and out u If you can just annotate the 0 码力 | 46 页 | 775.02 KB | 6 月前3
Mastering C++ ModulesSoftware Solutions6 Where did CMake come from? • Kitware was the lead engineering team for the Insight Segmentation and Registration Toolkit (ITK) http://www.itk.org – tasked with making it build on0 码力 | 77 页 | 9.07 MB | 6 月前3
Practical memory pool based allocators for Modern C++unpractical to do for a real application ○ It would lack the call site information which would limit the insight users can get about where and why allocations happen, making the debugging and reasoning harder0 码力 | 49 页 | 986.95 KB | 6 月前3
共 101 条
- 1
- 2
- 3
- 4
- 5
- 6
- 11













