Coding Standards and Performance Optimization

In the latest code review done by chx and Morbus at http://www.drupaltoughlove.com, one of the items commented on was the usage of "else if" instead of "elseif". There's nothing in the Coding Standards doc that specifically states that one should be used over the other, however it is "implied" from the first example on indentation that "elseif" should be used. Can the Coding Standards doc be updated so that it states one way or the other? Personally I don't mind which, but I would prefer if there was consistency. Core itself has a mixture, but with a higher number of "elseif".

In the Doxygen formatting conventions doc, it says that files should be documented with the @file directive and gives the following example:

Note the @file line in particular.

More and more contrib modules are including JavaScript files, so I want to add the ability to review JavaScript files to the Coder module. However, step 1 is we need to agree on what coding standards we should be using for JavaScript.

Moved to official ideas list

What I wanna develop for SOC 2008 is a module called security (or add security function to simpletest existing module) to enable users checking their drupal installation against xss and sql injection vulnerabilities.
It will be also good for module developers, in fact they can check their module before submitting them to drupal website. Users could be more protected against vulnerabilities that became from third part modules.
The objective of this work is to realize automated penetration test on drupal installation.

It will be based upon SimpleTest, already used by Rasmus (php core developer) to develop his own closed source xss scanner. SimpleTest is a jUnit similar library written for php.

My module could easily been extended to add more functionalities about security, but basically I think that this two are the most important.
If someone has functionality ideas to improve my project and make it better I'm here, listening for more proposal.

This article I wrote should appeal to people interested in high performance Drupal sites. Most of the performance gains are achieved by doing things with the Javascript and Drupal's File API.

http://wimleers.com/article/improving-drupals-page-loading-performance

You can expect another article soon, about the same topic, but then putting it to practice. I'll use the CDN integration module (of which I'm also the maintainer) and the included core patches to do it in just a few simple steps.

Hi,
I need a table for #127, so it will go here :)
This table is now fully complete :)

<

table>

Index with 30 nodes No 3.64 55.13 3.42

normal 136.62

In case you don't know, Edward Z. Yang (ezyang) is squashing a lot of bugs in coder_format in the scope of a GHOP task currently.
In case you don't know coder_format, it's a script I wrote some time ago which re-formats one PHP file, or recursively all files in a directory according to Drupal's Coding Standards. Doug Green has been so kind to add it to the Coder module, so if you are a Drupal developer, you probably have (an out-dated version of) it already. Unfortunately, it did not receive that much attention yet.

I do not yet want to promote coder_format with this post. Today, I just want to show you the results of an experiment, which in turn will show you, what you can expect from coder_format.

Guess, what this ugly code snippet is:

This page is for tracking the findings of GHOP #136 in coder_format of the coder module.

This is my GHOP task, for further information look at http://drupal.org/node/196907

The Text from there ;)
For GHOP Drupal-Issue 4 I did a profiling of D6.
The Comp Specs are:
Core2Duo E6320 (overclocked, both Cores 2,24Ghz)
4GB Mem
HDD - don't know :P should be 72000rpm, 8MB Cache or so
Gentoo Linux, Kernel 2.6.21-tuxonice-gentoo-r6 running X
1. Analysis of a fresh installed D6-HEAD (12.09.07) start page after installing (runned cron 1 time manually, please note that the standard page IS NOT saved into db)

Overall stats:

Draft list from chx:


function node_node_operations() {
function node_operations_publish($nodes) {
function node_operations_unpublish($nodes) {
function node_operations_promote($nodes) {
function node_operations_demote($nodes) {
function node_operations_sticky($nodes) {
function node_operations_unsticky($nodes) {
function node_filters() {
function node_build_filter_query() {
function node_filter_form() {
function theme_node_filter_form($form) {
function theme_node_filters($form) {
function node_filter_form_submit($form, &$form_state) {