Alex Thottunkel
- Total activity 2329
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 1176
Articles
Recent activity by Alex Thottunkel Sort by recent activity-
phpinfo() should not be used in production
Why you should care For security purpose, developers should not leave phpinfo() in production code, as it displays information which can be used to compromise the server that your site is running ...
-
Avoid useless overriding method
Why you should care Overring methods is a very powerfull way of factoring the code and produce complete fonctionnalities. However useless overriding methods can be a problem for the simplicity of ...
-
The code contains too many uppercase control structure keywords
Why you should care For code readability and naming consistency, below control structure keywords should be in lower cases: if else elseif foreach for do-while while try catch ...
-
The code contains too many PHP4 deprecated constructor naming.
Why you should care Developers should avoid using deprecated constructors. Since PHP5, constructor should be named __construct. How we detect CAST Highlight counts one occurrence each time: a ...
-
The code contains too many functions, interfaces or classes with closing not commented
Why you should care For better code maintainability, functions, interfaces and classes should end with a comment. How we detect CAST Highlight counts one occurrence each time a function, an inter...
-
The code contains too many functions throwing exceptions that have inconsistencies in "@throws" tags
Why you should care Every function that throws exceptions must have a throw tag. How we detect CAST Highlight counts one occurrence each time a function throwing an exception has no @Throws tag. ...
-
The code contains too many functions not complying with naming conventions
Why you should care Complying with naming conventions make the source code easier to ready and so to maintain. Function names should start with an upper case and should not contain underscores OR ...
-
The code contains too many final artifacts in final classes
Why you should care Unnecessary final modifiers inside final classes should be avoided. Final modifier prevents child classes from overriding a method by prefixing the definition with final. If th...
-
The code contains too many classes that declare __get() without declaring __set()
Why you should care When __get() are declared, __set() shoud be declared as well. How we detect CAST Highlight counts one occurrence each time a __get() is detected in source code without an asso...
-
The code contains too many class names that do not begin with an uppercase letter
Why you should care Complying with naming conventions make the source code easier to ready and so to maintain. Class names should start with an upper case. How we detect CAST Highlight counts one...