- Use case: Blog posts and books, not documentation for software.
- As much code as possible should be included within the Markdown file.
- I’m currently using
§
as a meta-character.- I’m open to alternatives. Other characters I considered:
¡ ¿ Δ ≡
- I wanted it to be a non-ASCII character, to minimize the risk of conflicts.
- I’m open to alternatives. Other characters I considered:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
require "formula" | |
class KitchenSync < Formula | |
homepage "https://github.com/willbryant/kitchen_sync" | |
url "https://github.com/willbryant/kitchen_sync/archive/0.47.tar.gz" | |
sha1 "b222273ca35be5e6d9dd609cd1532d204c88cee0" | |
depends_on "cmake" => :build | |
depends_on "boost" | |
depends_on "yaml-cpp" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
def sign(number) | |
if number > 0 | |
return 1 | |
elsif number < 0 | |
return -1 | |
end | |
0 | |
end |