http://users.ece.cmu.edu/~koopman/stack_computers/index.html
This file contains hidden or 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
| F;G;H;F,0;G,0;H,0;0,F;F,F;G,F;H,F;8,F;u,F;v,F;w,F;x,F;0,G;F,G;G,G;H,G;8,G;u,G;v,G;w,G;x,G;0,H;F,H;G,H;H,H;8,H;u,H;v,H;w,H;x,H;F,8;G,8;H,8;F,u;G,u;H,u;F,v;G,v;H,v;F,w;G,w;H,w;F,x;G,x;H,x;F,0,0;G,0,0;H,0,0;0,F,0;8,F,0;u,F,0;v,F,0;w,F,0;x,F,0;0,G,0;8,G,0;u,G,0;v,G,0;w,G,0;x,G,0;0,H,0;8,H,0;u,H,0;v,H,0;w,H,0;x,H,0;F,u,0;G,u,0;H,u,0;F,v,0;G,v,0;H,v,0;F,w,0;G,w,0;H,w,0;F,x,0;G,x,0;H,x,0;0,0,F;F,0,F;G,0,F;H,0,F;8,0,F;u,0,F;v,0,F;w,0,F;x,0,F;0,F,F;8,F,F;9,F,F;d,F,F;E,F,F;u,F,F;v,F,F;w,F,F;x,F,F;0,G,F;8,G,F;9,G,F;d,G,F;E,G,F;u,G,F;v,G,F;w,G,F;x,G,F;0,H,F;8,H,F;9,H,F;d,H,F;E,H,F;u,H,F;v,H,F;w,H,F;x,H,F;0,8,F;8,8,F;u,8,F;v,8,F;w,8,F;x,8,F;F,9,F;G,9,F;H,9,F;F,d,F;G,d,F;H,d,F;F,E,F;G,E,F;H,E,F;0,u,F;F,u,F;G,u,F;H,u,F;8,u,F;u,u,F;v,u,F;w,u,F;x,u,F;0,v,F;F,v,F;G,v,F;H,v,F;8,v,F;u,v,F;v,v,F;w,v,F;x,v,F;0,w,F;F,w,F;G,w,F;H,w,F;8,w,F;u,w,F;v,w,F;w,w,F;x,w,F;0,x,F;F,x,F;G,x,F;H,x,F;8,x,F;u,x,F;v,x,F;w,x,F;x,x,F;0,0,G;F,0,G;G,0,G;H,0,G;8,0,G;u,0,G;v,0,G;w,0,G;x,0,G;0,F,G;8,F,G;9,F,G;d,F,G;E,F,G;u,F,G;v,F,G;w,F,G;x,F,G;0,G,G;8,G, |
This file contains hidden or 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
| // Schmidhuber's neural bucket brigade | |
| struct Incomming { | |
| int n; | |
| int *idxArr; | |
| }; | |
| struct Ctx { | |
| float lamda; | |
| float *xtm1; |
This file contains hidden or 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
| // there is an artifact pattern which could be interpreted as an melody | |
| #define uint32_t uint | |
| // rule 30 | |
| uint32_t ca_rule30(uint32_t v) { | |
| uint32_t left = (v << 31) | (v >> 1); | |
| uint32_t center = v; |
http://framerd.org | object oriented database
This file contains hidden or 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
| Richard Loosemore | |
| 22. Mai um 20:21 | |
| Okay, this is driving me crazy and I apologize for bothering people here, but what is the term used for those regions of a big codebase that are have been put off limits, because fixing bugs in those areas only causes more bugs to crop up elsewhere? "Unmaintainable code" is used, but I could have sworn that there was another term for "do not touch" regions? | |
| Gefällt mirKommentierenTeilen | |
| Kommentare | |
| Richard Loosemore | |
| Richard Loosemore I wanted to use it as an example of where complicated shades off into complexity. | |
| Gefällt mir · Antworten · 22. Mai um 20:22 | |
| Mike Sellers | |
| Mike Sellers I know what you mean (and "frozen" as Peter Rothman said below is what I've seen used in the past), but this isn't exactly the difference between complicated and complex. Very briefly, the difference I've seen referenced (and use myself) is that a complicated process is one with lots of links or connections, but they're all linear: none recur to create loops. Complex processes necessarily have loop |