| # import config. | |
| # You can change the default config with `make cnf="config_special.env" build` | |
| cnf ?= config.env | |
| include $(cnf) | |
| export $(shell sed 's/=.*//' $(cnf)) | |
| # import deploy config | |
| # You can change the default deploy config with `make cnf="deploy_special.env" release` | |
| dpl ?= deploy.env | |
| include $(dpl) |
| LIBRARY WRITING REFERENCE LIST | |
| =============================== | |
| 1.) Designing and Evaluating Reusable Components (Casey Muratori: http://mollyrocket.com/casey/stream_0028.html) | |
| ---------------------------------------------------------------------------------------------------------------- | |
| _THE_ reference on API design up to this day on the internet. Nobody should write a library without having seen this. | |
| I come back to this talk every N number of weeks it is that good. | |
| 2.) stb_howto (Sean Barrett: https://github.com/nothings/stb/blob/master/docs/stb_howto.txt) | |
| -------------------------------------------------------------------------------------------- | |
| Sean Barretts single header libraries (https://github.com/nothings/stb) was the first time for me that I came across |
| #include "mu.h" | |
| #define _CRT_SECURE_NO_WARNINGS | |
| #include <malloc.h> | |
| #define _USE_MATH_DEFINES | |
| #include <math.h> | |
| #define _NO_CRT_STDIO_INLINE | |
| #include <stdio.h> | |
| #include <stdarg.h> | |
| #define NO_STRICT |
| // | |
| // RecordAudio.swift | |
| // | |
| // This is a Swift class (updated for Swift 5) | |
| // that uses the iOS RemoteIO Audio Unit | |
| // to record audio input samples, | |
| // (should be instantiated as a singleton object.) | |
| // | |
| // Created by Ronald Nicholson on 10/21/16. | |
| // Copyright © 2017,2019 HotPaw Productions. All rights reserved. |
| # template.py btree.inl => btree.h, btree.out.inl | |
| import re | |
| import sys | |
| import os | |
| import os.path | |
| if len(sys.argv) != 2: | |
| print "Usage: template.py <filename>" | |
| sys.exit(1) |
| # template.py btree.inl => btree.h, btree.out.inl | |
| import re | |
| import sys | |
| import os | |
| import os.path | |
| if len(sys.argv) != 2: | |
| print "Usage: template.py <filename>" | |
| sys.exit(1) |
| // Here is btree.inl, which is the thing you would write yourself. | |
| // Unlike C++ templates, the granularity of these lightweight templates is at the | |
| // module level rather than the function or class level. You can think of it like | |
| // ML functors (parameterized modules) except that there isn't any static checking | |
| // of signatures (in that respect, it's like C++ templates). In my view, this style | |
| // of parameterized generative modules is generally the better conceptual framework. | |
| // This is a completely valid C file even prior to preprocessing, so during library | |
| // development you can just include this file directly. That is a big win for testing |
Orthodox C++ (sometimes referred as C+) is minimal subset of C++ that improves C, but avoids all unnecessary things from so called Modern C++. It's exactly opposite of what Modern C++ suppose to be.
