chiguire

{"gameLink":"GGJ19: When I Saw it","canvasses":[[5,"f",16,"0",13,"f",35,"0",5,"f",6,"0",1,"f",22,"0",42,"f",4,"0",5,"f",11,"0",16,"f",13,"0",7,"f",9,"0",2,"f",17,"0",3,"f",2,"0",1,"f",7,"0",11,"f",9,"0",32,"f",14,"0",14,"f",53,"4",3,"0",11,"f",14,"0",19,"f",11,"0",24,"f",1,"0",15,"f",9,"0",1,"4",1,"9",3,"4",1,"9",1,"4",1,"9",2,"4",1,"9",1,"4",3,"9",1,"4",1,"9",3,"4",1,"9",2,"4",3,"9",3,"4",3,"9",2,"4",2,"9",2,"4",1,"9",3,"4",1,"9",2,"4",3,"9",1,"4",3,"9",1,"4",1,"1",3,"f",23,"0",1,"f",10,"0",18,"f",14,"0",6,"f",8,"0",3,"f",2,"0",8,"f",10,"0",1,"4",1,"9",3,"4",1,"9",1,"4",1,"9",2,"4",1,"9",1,"4",1,"9",3,"4",2,"9",2,"4",1,"9",3,"4",1,"9",3,"4",1,"9",4,"4",1,"9",2,"4",1,"9",1,"4",1,"9",3,"4",1,"9",3,"4",1,"9",3,"4",1,"9",2,"4",1,"1",3,"0",23,"f",33,"0",5,"f",11,"0",11,"f",1,"0",13,"f",4,"0",2,"f",1,"4",1,"9",1,"4",1,"9",1,"4",1,"9",1,"4",4,"9",1,"4",2,"9",2,"4",1,"9",1,"4",1,"9",1,"4",1,"9",3,"4",1,"9",4,"4",2,"9",2,"4",4,"9",1,"4",1,"9",1,"4",1,"9",1,"4",1,"9",3,"4",1,"9",3,"4",1,"9",2,"4",1,"1",33,"f",10,"0",4

Kerollmops

Core Coding Standard

Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.

Table Of Contents

• Why we need Coding Standards
• Context is Important
• Stylistic Standards

• Namespaces