| #.rst: | |
| # FindOracle | |
| # ---------- | |
| # | |
| # Configure Oracle libraries | |
| # | |
| # ORACLE_FOUND - system has Oracle OCI | |
| # ORACLE_HAS_XML - Oracle has XDK support(thick client installed) | |
| # ORACLE_INCLUDES - where to find oci.h | |
| # ORACLE_LIBRARIES - the libraries to link against to use Oracle OCI |
Based on https://www.gnu.org/software/make/manual/html_node/Quick-Reference.html
| Directive | Description |
|---|---|
define variable define variable = define variable := define variable ::= define variable += define variable ?= endef |
Define multi-line variables. |
undefine variable |
Undefining variables. |
When I was working on a generic port of Google's hashmap to C, I wrote a function that (ignoring irrelevant parts) looked like this:
typedef struct {
uint8_t *bytes;
size_t len;
} bytebuf;
| #include <time.h> | |
| #include <stdio.h> | |
| #include <errno.h> | |
| #include <stdlib.h> | |
| #include <stdint.h> | |
| #include <sys/random.h> | |
| #define UUID_T_LENGTH (16) | |
| #define UNIX_TS_LENGTH (6) |
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
Here's a list of mildly interesting things about the C language that I learned mostly by consuming Clang's ASTs. Although surprises are getting sparser, I might continue to update this document over time.
There are many more mildly interesting features of C++, but the language is literally known for being weird, whereas C is usually considered smaller and simpler, so this is (almost) only about C.
struct foo {
struct bar {
int x;
To remove a submodule you need to:
The package linked to from here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
All input coming from user interaction, such mouse click. are directed to the Controller first. The Controller then kick off some functionality. A single Controller may render many different Views based on the operation being executed. Also view doesn’t have any knowledge of or reference to the Controller. Controller interact with the Model and pass the model to the View. So there is a knowledge between the View and Model being passed on to it.
The input is directed to the View. View hold a reference to the ViewModel. But ViewModel is not aware of the View. So it is possible to have one ViewModel to support many Views. Also the Model is decoupled from the View. ViewModel interact with the Model and feed the View with the data.
The CommonJS format is used in Node.js and uses require and module.exports to define dependencies and modules. CommonJS modules were designed with server development in mind. Naturally, the API is synchronous. In other words, modules are loaded at the moment and in the order they are required inside a source file.
The AMD format is used in browsers and uses a define function to define modules. The main difference between AMD and CommonJS lies in its support for asynchronous module loading. Asynchronous loading is made possible by using JavaScript's traditional closure idiom: a function is called when the requested modules are finished loading. Module definitions and importing a module is carried by the same function: when a module is defined its dependencies are made explicit.
