0.9.5
Changes:
- For what should be the last time, major syntax changes have occurred in MD. Gone now are the strange nodes - ModDamage is now entirely conditionally driven. The new configuration scheme is like follows:
Event:
- SOME.ROUTINE
0.9.5
Changes:
Event:
- SOME.ROUTINE
Syntax: asdf.asdf.#asdf
Description: asdf
Example:
asdf:
- 'asdf'
Aliases: Material: pickaxe: - WOOD_PICKAXE - STONE_PICKAXE - IRON_PICKAXE - GOLD_PICKAXE - DIAMOND_PICKAXE spade:
##Features
Bunnyhop
Trimp jumping (requires 2 successful bunnyhops before use)
Ramp-jumping
Voteable ingame for manual, easy manual, and automatic bunnyhopping.
One of Dr. Welborn's best pieces of advice to novice programmers. :) It takes real skill, no matter what testing method you use, to test (and by extension, debug) effectively!
Many of you have the wrong idea of what testing is. Many of you mistakenly believe testing is the process of proving your code is correct. If you approach testing with the mindset that you're going to prove your code is correct, you most likely will. No matter how many bugs you have. Testing is based on the Scientific Method. Forgotten the Scientific Method, here is a recap:
- Observe a System
- Build a theory or model that explains the System
- Use the theory/model to make predictions about the System
- Verify the theory/model is correct by comparing predicted results with actual results
# This script assumes you're using a GNU-compliant Make implementation. | |
# It is required that the following in your path: | |
# - bash | |
# Otherwise, this script attempts to use native commands. | |
# Help from [here](http://stackoverflow.com/questions/4555120/obtaining-directory-makefile-resides-in) | |
THIS_MAKEFILE_PATH:=$(word $(words $(MAKEFILE_LIST)),$(MAKEFILE_LIST)) | |
POSIX_DIR="$(shell cd $(dir $(THIS_MAKEFILE_PATH));pwd)" | |
UNAME=$(shell uname -o) | |
ifeq ($(OS),Windows_NT) |
# Shamelessly copied and adapted from https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfiles-git-bare-repo/ | |
pushd "$HOME" > /dev/null | |
git clone --bare https://github.com/ErichDonGubler/.dotfiles.git ~/.dotfiles.git | |
function .git() { | |
git --git-dir="$HOME/.dotfiles.git/" --work-tree="$HOME" $* | |
} | |
.git checkout | |
if [ $? = 0 ]; then | |
echo "Checked out dotfiles."; | |
else |
/** | |
* Demo: duckConstraints.d | |
* Purpose: Demonstrate duck-typed constraints in D (in response to https://maikklein.github.io/2016-03-01-metaprogramming-typeobject/) | |
* Authors: Erich Gubler (Github: @erichdongubler) | |
* Date: 6/25/2016 | |
* | |
* @maikklein: "Constrains" ( ;) ) in D similar to the Rust block you have shown: | |
* | |
* impl<T> Bar<T> | |
* where: T: Copy |
This gist documents Erich's endeavors to get QML working with Rust on his machines, since there's not much in the way of a helpful tutorial.
WARNING: Work in progress. Definitely not complete!
To get gcc
/make
/cmake
, we'll need to...what? Building qml-rust
with the Win-builds version of GCC seems to make the build report gcc
as broken (see here).
Install Qt with the open-source license for versions 5.6-5.8 here.
I hereby claim:
To claim this, I am signing this object: