Quote:
No they don't, and I never said they do.
Just wanted to point out that it is possible, although I guess nobody would ever even think of proofing their Code.
This is only being done for really important software like some parts or Aircraft Firmware.
|
Good point. Less important software we can always debug later...

If there is a need for it.
Quote:
As a new coder (who is not afraid to ask for help), I can assure you that I will gladly take the assistance/advice of someone posting to help me LONG before someone cutting my head off so that their ego is satisfied (again, reference TONE).
|
Hey, where'd you get head cutting part from? :P
Quote:
Wow you seem to be getting a bit stressed there, you might wanna reel in that temper just a little bit, i mean after all asking to judge peoples hacks and you can't even muster up the people skills to last a debate on the concept, ouch, this site would really be going down hill.
|
You see, anybody would get annoyed when someone "glues" irrelevant pieces of text together and waves them in front of your nose. You are wrong though, I am not getting stressed out. Now as I said, shut the f*ck up. Thanks.
Quote:
The 2nd one complies with vBulletin coding standards.
|
Good, the we use the 2nd one.
Quote:
Who is really going to open the code up and say 'damn, I wish I would have known this didnt use the coding standards before I installed it!'.
|
The coders will. I'd like you to recall the coding style of vBulletin 2 and compare it with vBulletin 3. Which one is easier to modify? This:
PHP Code:
if ($a) {
while ($b = $c)
{
echo "!!!!!"; }
}
else { print "yo";
}
or this
PHP Code:
if ($a)
{
while ($b = $c)
{
echo "!!!!!";
}
}
else
{
print "yo";
}
There you go.