https://sourceforge.net/adobe/flexsdk/wiki/Coding%2520Guidelines/Recent changes to Coding GuidelinesenTue, 20 Mar 2012 12:41:41 -0000https://sourceforge.net/adobe/flexsdk/wiki/Coding%2520Guidelines/<pre>--- v1 +++ v2 @@ -4,16 +4,15 @@ * **Architecture**: Does the code follow the broader architectural design? * **API**: Is the API consistent? - * **[Code format and convention](http://opensource.adobe.com/wiki/display/flexsdk/Coding%2BConventions)**: Does the code follow standard formatting and code conventions? + * **[Code format and convention](https://sourceforge.net/adobe/flexsdk/wiki/Coding%20Conventions/)**: Does the code follow standard formatting and code conventions? * **Use Cases**: Does the code handle all use cases? * **ASDoc**: Do we need to add ASDoc comments? * **Readability**: Is the code understandable/maintainable? Would more comments help? * **Duplication**: Are we duplicating code that could be combined? * **Backward compatibility**: Does the code break backward compatibility? * **Performance**: Does the code minimize memory, swf size, and runtime performance impact? * **Dependencies**: Do the changes introduce undesirable dependencies or layer violations (e.g. link in unnecessary classes into base classes, etc.)? * **Cross-Platform**: Are there cross-platform, cross-browser, or cross-runtime (including AIR) issues to consider? * **Security**: Does the code raise any security issues? - </pre>pallab jyotee hazarikaTue, 20 Mar 2012 12:41:41 -0000https://sourceforge.net0aa808d45332946b8ce13e48b001c6e5c7c35198https://sourceforge.net/adobe/flexsdk/wiki/Coding%2520Guidelines/# Coding Guidelines This checklist should be used when contributing code to the Flex SDK: * **Architecture**: Does the code follow the broader architectural design? * **API**: Is the API consistent? * **[Code format and convention](http://opensource.adobe.com/wiki/display/flexsdk/Coding%2BConventions)**: Does the code follow standard formatting and code conventions? * **Use Cases**: Does the code handle all use cases? * **ASDoc**: Do we need to add ASDoc comments? * **Readability**: Is the code understandable/maintainable? Would more comments help? * **Duplication**: Are we duplicating code that could be combined? * **Backward compatibility**: Does the code break backward compatibility? * **Performance**: Does the code minimize memory, swf size, and runtime performance impact? * **Dependencies**: Do the changes introduce undesirable dependencies or layer violations (e.g. link in unnecessary classes into base classes, etc.)? * **Cross-Platform**: Are there cross-platform, cross-browser, or cross-runtime (including AIR) issues to consider? * **Security**: Does the code raise any security issues? SourceForge Editorial StaffThu, 15 Mar 2012 18:12:18 -0000https://sourceforge.net19bdf6b8edccf8d218a74dfaddad9afc0fd6d832