Examine individual changes
This page allows you to examine the variables generated by the Abuse Filter for an individual change.
Variables generated for this change
| Variable | Value |
|---|---|
Edit count of the user (user_editcount) | 0 |
Name of the user account (user_name) | 'HeckYeah100' |
Age of the user account (user_age) | 1904414 |
Page ID (page_id) | 0 |
Page namespace (page_namespace) | 0 |
Page title (without namespace) (page_title) | 'Non' |
Full page title (page_prefixedtitle) | 'Non' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | '' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '' |
New page wikitext, after the edit (new_wikitext) | '== Non ==
This programming language is designed for people who want to purposfully hurt their brains. Similar to BF, it is intentionally designed to hurt.
===CHARACTERS===
the characters of non are the following:.
^ //increments the object on stack.
, //decrements the object on stack.
p; //pops the object on stack and displays it, think of it as like the print function in most modern programming languages
s; //number sets a number, defined after the ;, and adds it to the top of the stack
c; //clears the stack.
p; //noop is a variation of p; that pops the last value but doesn't print, it is effectively a discard function.
m; //sets the top of the stack to a random memory spot, and prints the memory spots name. the memory location could potentially be called anything from 'i like flowers' to 'tyu4w8953ptyyhg4s87gr'
===SYNTAX===
Now, your probably thinking,"wait, this is pretty easy!" But, of course, there is a catch. You can't call
^
//after
,
OR call a
^ //'''directly''' after a
p
Not only that, but if you clear the stack, you cant use
p; noop
anymore for the duration of the program, and you also cant use
,
after calling
s
If these rules are not followed, the compiler discards any output once seeing the syntax error, and also ''clears'' the editor, so making a tiny syntax fumble on a big program could cost you the ENTIRE PROGRAM.
===USAGE===
Although the syntax rules are diabolical, saying something simple like hello world is easy, or atleast in ascii;
s; 72 p;
s; 101 p;
s; 108 p;
s; 108 p;
s; 111 p;
s; 32 p;
s; 87 p;
s; 111 p;
s; 114 p;
s; 108 p;
s; 100 p;' |
Unified diff of changes made by edit (edit_diff) | '@@ -1,0 +1,45 @@
+== Non ==
+This programming language is designed for people who want to purposfully hurt their brains. Similar to BF, it is intentionally designed to hurt.
+===CHARACTERS===
+the characters of non are the following:.
+ ^ //increments the object on stack.
+
+ , //decrements the object on stack.
+
+ p; //pops the object on stack and displays it, think of it as like the print function in most modern programming languages
+
+ s; //number sets a number, defined after the ;, and adds it to the top of the stack
+
+ c; //clears the stack.
+
+ p; //noop is a variation of p; that pops the last value but doesn't print, it is effectively a discard function.
+
+ m; //sets the top of the stack to a random memory spot, and prints the memory spots name. the memory location could potentially be called anything from 'i like flowers' to 'tyu4w8953ptyyhg4s87gr'
+===SYNTAX===
+Now, your probably thinking,"wait, this is pretty easy!" But, of course, there is a catch. You can't call
+ ^
+ //after
+ ,
+OR call a
+ ^ //'''directly''' after a
+ p
+Not only that, but if you clear the stack, you cant use
+ p; noop
+anymore for the duration of the program, and you also cant use
+ ,
+after calling
+ s
+If these rules are not followed, the compiler discards any output once seeing the syntax error, and also ''clears'' the editor, so making a tiny syntax fumble on a big program could cost you the ENTIRE PROGRAM.
+===USAGE===
+Although the syntax rules are diabolical, saying something simple like hello world is easy, or atleast in ascii;
+ s; 72 p;
+ s; 101 p;
+ s; 108 p;
+ s; 108 p;
+ s; 111 p;
+ s; 32 p;
+ s; 87 p;
+ s; 111 p;
+ s; 114 p;
+ s; 108 p;
+ s; 100 p;
' |
New page size (new_size) | 1624 |
Old page size (old_size) | 0 |
Lines added in edit (added_lines) | [
0 => '== Non ==',
1 => 'This programming language is designed for people who want to purposfully hurt their brains. Similar to BF, it is intentionally designed to hurt.',
2 => '===CHARACTERS===',
3 => 'the characters of non are the following:.',
4 => ' ^ //increments the object on stack.',
5 => '',
6 => ' , //decrements the object on stack.',
7 => '',
8 => ' p; //pops the object on stack and displays it, think of it as like the print function in most modern programming languages ',
9 => '',
10 => ' s; //number sets a number, defined after the ;, and adds it to the top of the stack',
11 => '',
12 => ' c; //clears the stack.',
13 => '',
14 => ' p; //noop is a variation of p; that pops the last value but doesn't print, it is effectively a discard function.',
15 => '',
16 => ' m; //sets the top of the stack to a random memory spot, and prints the memory spots name. the memory location could potentially be called anything from 'i like flowers' to 'tyu4w8953ptyyhg4s87gr'',
17 => '===SYNTAX===',
18 => 'Now, your probably thinking,"wait, this is pretty easy!" But, of course, there is a catch. You can't call ',
19 => ' ^',
20 => ' //after ',
21 => ' , ',
22 => 'OR call a ',
23 => ' ^ //'''directly''' after a ',
24 => ' p',
25 => 'Not only that, but if you clear the stack, you cant use ',
26 => ' p; noop',
27 => 'anymore for the duration of the program, and you also cant use ',
28 => ' ,',
29 => 'after calling ',
30 => ' s',
31 => 'If these rules are not followed, the compiler discards any output once seeing the syntax error, and also ''clears'' the editor, so making a tiny syntax fumble on a big program could cost you the ENTIRE PROGRAM. ',
32 => '===USAGE===',
33 => 'Although the syntax rules are diabolical, saying something simple like hello world is easy, or atleast in ascii;',
34 => ' s; 72 p;',
35 => ' s; 101 p;',
36 => ' s; 108 p;',
37 => ' s; 108 p;',
38 => ' s; 111 p;',
39 => ' s; 32 p;',
40 => ' s; 87 p;',
41 => ' s; 111 p;',
42 => ' s; 114 p;',
43 => ' s; 108 p;',
44 => ' s; 100 p;'
] |
Unix timestamp of change (timestamp) | '1763755708' |