<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I ran this test just to see what would happen, and here are the
results, feel free to test it yourself. According to this test,
running a simple loop with one if statement 100k times, you lose about
20ms using uppercase. What is interesting, is that the same test in
php5 runs 100ms faster. <br>
<br>
slantview:~ steverude$ /Applications/xampp/xamppfiles/bin/php-4.4.7
test.php <br>
Time for UPPERCASE: 723.675251007 ms<br>
<br>
Time for lowercase: 702.354669571 ms<br>
<br>
slantview:~ steverude$ /Applications/xampp/xamppfiles/bin/php-5.2.2
test.php <br>
Time for UPPERCASE: 622.086286545 ms<br>
<br>
Time for lowercase: 607.203245163 ms<br>
<br>
<br>
Another interesting stat is that we have 2383 times in a stock drupal
5.1 distribution where we use an uppercase TRUE, FALSE or NULL.<br>
<br>
Reference:<br>
<br>
slantview:~/Documents/workspace/drupal-5.1 steverude$ grep -r TRUE * |
wc -l<br>
629<br>
slantview:~/Documents/workspace/drupal-5.1 steverude$ grep -r FALSE * |
wc -l<br>
511<br>
slantview:~/Documents/workspace/drupal-5.1 steverude$ grep -r NULL * |
wc -l<br>
1243<br>
<br>
So it does not seem that unreasonable to me that we could potentially
get some performance gain by standardizing on lower case true, false
and null. Preference aside (me being on the uppercase side), I believe
that adding this standard to the drupal standards could potentially
give us a small amount of performance increase.<br>
<br>
I also think the issue should be documented in the coding standard and
reflected in the Coder module regardless of the decision.<br>
<br>
Here is the code for the test:<br>
<br>
slantview:~ steverude$ cat test.php <br>
<?php<br>
<br>
function microtime_float() {<br>
list($usec, $sec) = explode(" ", microtime());<br>
return ((float)$usec + (float)$sec);<br>
}<br>
<br>
$var = true;<br>
<br>
$time_total = 0;<br>
for ($i = 0; $i < 100000; ++$i) {<br>
$time_start = microtime_float();<br>
if ($var === TRUE) {<br>
$time_end = microtime_float();<br>
$time_total += $time_end - $time_start;<br>
}<br>
}<br>
$time_total = $time_total * 1000;<br>
print "Time for UPPERCASE: $time_total ms\n\n";<br>
<br>
$time_total = 0;<br>
for ($i = 0; $i < 100000; ++$i) {<br>
$time_start = microtime_float();<br>
if ($var === true) {<br>
$time_end = microtime_float();<br>
$time_total += $time_end - $time_start;<br>
}<br>
}<br>
$time_total = $time_total * 1000;<br>
print "Time for lowercase: $time_total ms\n\n";<br>
<br>
Thanks,<br>
<br>
Steve Rude<br>
<br>
Karoly Negyesi wrote:
<blockquote cite="mid:E1IPjOm-0004Rl-GH@fenris.runbox.com" type="cite">
<pre wrap="">I do not believe that true could be faster than TRUE when php is case agnostic about its identifiers. Maybe there is time taken to lowercase TRUE ... but if you can measure lowercasing four characters in the parsing stage where only ASCII is supported, congratulations.
About commas, yes the D5 menu defintiions are ugly sometimes. Have you seen D6 :) ?
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Steve Rude
+ Lead Developer</font><br>
<b><font color="#ff3300" face="Verdana, Arial, Helvetica, sans-serif"
size="2">Achieve<font color="#666666">Internet</font></font></b><a><br>
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">(800)
618-877 x 202</font><br>
<br>
<font face="Verdana, Arial, Helvetica, sans-serif" size="2">http://www.achieveinternet.com</font></a></div>
</body>
</html>