It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
--deletes in Document | |
--at this point all associated media files are deleted | |
delete from umbracoDomains where id in (select id from umbracoNode where path like '%-20%' and id!=-20); | |
delete from cmsDocument where nodeId in (select id from umbracoNode where path like '%-20%' and id!=-20); | |
--deletes in Content | |
delete from cmsPropertyData where contentNodeId in (select id from umbracoNode where path like '%-20%' and id!=-20); | |
delete from cmsPreviewXml where nodeId in (select id from umbracoNode where path like '%-20%' and id!=-20); | |
delete from cmsContentVersion where ContentId in (select id from umbracoNode where path like '%-20%' and id!=-20); | |
delete from cmsContentXml where NodeId in (select id from umbracoNode where path like '%-20%' and id!=-20); |
#include <lwan.h> | |
#include <lwan-template.h> | |
#include <strbuf.h> | |
struct thing { | |
lwan_tpl_list_generator_t generator; | |
const char *name; | |
}; |
Why do compilers even bother with exploiting undefinedness signed overflow? And what are those | |
mysterious cases where it helps? | |
A lot of people (myself included) are against transforms that aggressively exploit undefined behavior, but | |
I think it's useful to know what compiler writers are accomplishing by this. | |
TL;DR: C doesn't work very well if int!=register width, but (for backwards compat) int is 32-bit on all | |
major 64-bit targets, and this causes quite hairy problems for code generation and optimization in some | |
fairly common cases. The signed overflow UB exploitation is an attempt to work around this. |
This explains how to setup for GitHub projects which automatically generates Doxygen code documentation and publishes the documentation to the gh-pages
branch using Travis CI.
This way only the source files need to be pushed to GitHub and the gh-pages branch is automatically updated with the generated Doxygen documentation.
Get an account at Travis CI. Turn on Travis for your repository in question, using the Travis control panel.
To create a clean gh-pages
branch, with no commit history, from the master branch enter the code below in the Git Shell. This will create a gh-pages branch with one file, the README.md
in it. It doesn't really matter what file is uploaded in it since it will be overwritten when the automatically generated documentation is published to th
$ python xor.py | |
Training: | |
Epoch 0 MSE: 1.765 | |
Epoch 100 MSE: 0.015 | |
Epoch 200 MSE: 0.005 | |
* Target MSE reached * | |
Evaluating: | |
1 XOR 0 = 1 ( 0.904) Error: 0.096 | |
0 XOR 1 = 1 ( 0.908) Error: 0.092 | |
1 XOR 1 = 0 (-0.008) Error: 0.008 |
From N1256: (See http://port70.net/~nsz/c/c99/n1256.html#J.2)
- A "shall" or "shall not" requirement that appears outside of a constraint is violated (clause 4).
- A nonempty source file does not end in a new-line character which is not immediately preceded by a backslash character or ends in a partial preprocessing token or comment (5.1.1.2).
- Token concatenation produces a character sequence matching the syntax of a universal character name (5.1.1.2).
- A program in a hosted environment does not define a function named
main
using one of the specified forms (5.1.2.2.1). - A character not in the basic source character set is encountered in a source file, except in an identifier, a character constant, a string literal, a header name, a comment, or a preprocessing token that is never converted to a token (5.2.1).
- An identifier, comment, string literal, character constant, or header name contains an invalid multibyte character or does not
set -g status-bg "colour236" | |
set -g message-command-fg "colour253" | |
set -g status-justify "left" | |
set -g status-left-length "100" | |
set -g status "on" | |
set -g pane-active-border-fg "colour109" | |
set -g message-bg "colour239" | |
set -g status-right-length "100" | |
set -g status-right-attr "none" | |
set -g message-fg "colour253" |