6 private links
WebSocket++ is a header only C++ library that implements RFC6455 The WebSocket Protocol. It allows integrating WebSocket client and server functionality into C++ programs. It uses interchangeable network transport modules including one based on C++ iostreams and one based on Boost Asio.
Runtime-Compiled C++ is a way to reliably make major changes to your C++ code at runtime and see the results immediately.
Implementation of bigint java class in c++
at&t syntax utilization example
A lightweight library allowing diverse unit types, seamless implicit scaling between them and the ability to work efficiently with multiple factor-less base unit systems (e.g. MKS and cgs).
inv.erase(
std::remove_if(
inv.begin(),
inv.end(),
[](http://IInventory* element) -> bool {
// Do "some stuff", then return true if element should be removed.
return true;
}
),
inv.end()
);
Sort algorithm with c++ algorithm
git subtree add --prefix dir git@git.git master
Videos about c++
Programming today exercises our symbolic reasoning. We write code—a sequence of symbols—in a text editor.
But when we explain ideas to colleagues, we don’t just speak words, we draw diagrams and gesture with our hands. We augment the symbolic channel with a spatial channel.
How can we communicate programs to a computer over a spatial channel?
Shadershop is an interface for programming GPU shaders in the mode of a direct manipulation image editor like Photoshop. It is an experiment in leveraging the programmer’s spatial reasoning the way that coding today leverages the programmer’s symbolic reasoning.
The automatic exploit generation challenge we address is given a program, automatically find security-critical bugs and generate exploits. Our approach uses a novel formal verification technique called preconditioned symbolic execution to make automatic exploit generation more scalable to real-world programs than without it.
When talking about pointers, we generally assume it is something that can be represented by void* pointer which has a size of 8 bytes on the x86_64 architecture.
Using a virtual dispatch might get relatively expensive in terms of clock cycles due to multiple levels of indirections including indirect branching as well as this pointer adjustment. Wise programmers do not use virtual dispatch without a good reason but oftentimes it is required either by design or when creating non-template reusable components/libraries and the final implementation of some parts of the program is not known.