| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| Version 2, December 2004 | |
| Copyright (C) 2011 Jed Schmidt <http://jed.is> | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. | |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
| main(argc, argv) | |
| int argc; | |
| char *argv[]; | |
| { | |
| int i; | |
| argc--; | |
| for(i=1; i<=argc; i++) | |
| printf("%s%c", argv[i], i==argc? '\n': ' '); | |
| } |
Delimited continuations manipulate the control flow of programs. Similar to control structures like conditionals or loops they allow to deviate from a sequential flow of control.
We use exception handling as another example for control flow manipulation and later show how to implement it using delimited continuations. Finally, we show that nondeterminism can also be expressed using delimited continuations.
| #include <Python.h> // Must be first | |
| #include <vector> | |
| #include <stdexcept> | |
| #include "PyUtils.h" | |
| using namespace std; | |
| // ===== | |
| // LISTS | |
| // ===== |
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
| module.exports = { | |
| get: function (req, res) { | |
| res.sendfile(req.path.substr(1)); | |
| }, | |
| _config: { | |
| rest: false, | |
| shortcuts: false | |
| } | |
| }; |
| /** | |
| * Takes a Sails Model object (e.g. User) and a ValidationError object and translates it into a friendly | |
| * object for sending via JSON to client-side frameworks. | |
| * | |
| * To use add a new object on your model describing what validation errors should be translated: | |
| * | |
| * module.exports = { | |
| * attributes: { | |
| * name: { | |
| * type: 'string', |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
