| *.dll | |
| *.exe | |
| *.obj | |
| *.so | |
| *.bin | |
| *.zip | |
| *.7z | |
| *.exp | |
| *.lib | |
| .vs/* |
There are times when you need to log off your Linux Desktop, and you want a process to run in the background. TMUX manages this very well.
For this example, let's suppose you're running a long running task like running rspecs on your project and
it is 5pm, and you need to go home.
| When you build on the Visual Studio command line, you must build the program in two steps. | |
| First, run cl /c /EHsc MyLib.cpp to compile the code and create an object file that's named MyLib.obj. | |
| (The cl command invokes the compiler, Cl.exe, and the /c option specifies compile without linking. For more information, see /c (Compile Without Linking).) | |
| Second, run lib MathFuncsLib.obj to link the code and create the static library MathFuncsLib.lib. | |
| (The lib command invokes the Library Manager, Lib.exe. For more information, see LIB Reference.) |
| /** | |
| * = Recursive descent parser = | |
| * | |
| * MIT Style License | |
| * By Dmitry Soshnikov <dmitry.soshnikov@gmail.com> | |
| * | |
| * In this short lecture we'll cover the basic (non-predictive, backtracking) | |
| * recursive descent parsing algorithm. | |
| * | |
| * Recursive descent is an LL parser: scan from left to right, doing |
| /* | |
| Ok, so you want to change your Object Type (or collision channel) to a custom channel in runtime. | |
| But there's a problem, it seems UE4 doesn't support this yet, but there's a workaround hehe :) | |
| For example, imagine you create the ObjectType Building. | |
| Now, imagine you want to change the ObjectType of all the StaticMeshComponents of the object OBJECT (from WorldStatic to Building, for example). | |
| You can try something like this: | |
| */ |
Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.
For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.
But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.
SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil