Comments on: Colon Syntax in PHP http://www.kwista.com/programming/colon-syntax-in-php/ Information Technology for Your Gee Whiz Collection Sat, 30 Oct 2010 06:51:45 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Tod Hansmann http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-32 Tod Hansmann Tue, 20 Apr 2010 18:26:18 +0000 http://www.kwista.com/?p=401#comment-32 Woops. No, I meant 4 spaces are less compiler efficient than one tab. It was backing up your point after refuting the reason you gave for your point. >.> Essentially, a compiler or interpreter is going to have to compare x number of spaces or y number of tabs. The less you have of either, the more efficient it can go through your code. It's going through byte by byte, so it makes sense. This is the same reason you see all the spaces taken out and all the var/function names reduced to as few characters as possible in some javascript on sites like google. On comps it doesn't amount to much. On things like OLD OLD OLD comps and cell phones, it can matter. Woops. No, I meant 4 spaces are less compiler efficient than one tab. It was backing up your point after refuting the reason you gave for your point. >.>

Essentially, a compiler or interpreter is going to have to compare x number of spaces or y number of tabs. The less you have of either, the more efficient it can go through your code. It’s going through byte by byte, so it makes sense. This is the same reason you see all the spaces taken out and all the var/function names reduced to as few characters as possible in some javascript on sites like google. On comps it doesn’t amount to much. On things like OLD OLD OLD comps and cell phones, it can matter.

]]> By: Chris London http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-28 Chris London Mon, 19 Apr 2010 21:28:14 +0000 http://www.kwista.com/?p=401#comment-28 That's interesting. I didn't know that tabs were less compiler efficient. It seems that that's how us programmers like it. More human friendly vs compiler efficient, like using functions and OOP. That’s interesting. I didn’t know that tabs were less compiler efficient. It seems that that’s how us programmers like it. More human friendly vs compiler efficient, like using functions and OOP.

]]> By: Tod Hansmann http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-27 Tod Hansmann Mon, 19 Apr 2010 21:00:48 +0000 http://www.kwista.com/?p=401#comment-27 Yeah, but I'll hand you 16 cents and cover all the hard drive space you'll use on spaces if you were to count every line of code you could waste that space on over the next 10 years. It IS less efficient for interpreters/compilers a bit. That DOES matter in things like PHP, albeit not in a noticeable manner. Yeah, but I’ll hand you 16 cents and cover all the hard drive space you’ll use on spaces if you were to count every line of code you could waste that space on over the next 10 years.

It IS less efficient for interpreters/compilers a bit. That DOES matter in things like PHP, albeit not in a noticeable manner.

]]> By: Chris London http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-26 Chris London Mon, 19 Apr 2010 20:27:22 +0000 http://www.kwista.com/?p=401#comment-26 Thanks for the comments. I TOTALLY agree with not using spaces. Some developer tools even replace the tabs you input with spaces. There are settings to turn this off which I recommend everyone turn off. Not only do tabs allow other developers to set the spacing to their liking but they take up less disk space. Correct me if I'm wrong but I'm pretty sure 1 tab takes up 1 byte and 1 space takes up 1 byte. So if you do a 5-spaces tab instead of just a regular tab then your tabs will take up 5 times as many bytes per tab! Thanks for the comments. I TOTALLY agree with not using spaces. Some developer tools even replace the tabs you input with spaces. There are settings to turn this off which I recommend everyone turn off.

Not only do tabs allow other developers to set the spacing to their liking but they take up less disk space. Correct me if I’m wrong but I’m pretty sure 1 tab takes up 1 byte and 1 space takes up 1 byte. So if you do a 5-spaces tab instead of just a regular tab then your tabs will take up 5 times as many bytes per tab!

]]> By: Tod Hansmann http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-25 Tod Hansmann Mon, 19 Apr 2010 19:57:55 +0000 http://www.kwista.com/?p=401#comment-25 I should note that "you" is not the fine people at Kwista >.> I should note that “you” is not the fine people at Kwista >.>

]]> By: Tod Hansmann http://www.kwista.com/programming/colon-syntax-in-php/comment-page-1/#comment-24 Tod Hansmann Mon, 19 Apr 2010 19:57:35 +0000 http://www.kwista.com/?p=401#comment-24 Gligh! It makes it look more like Perl. That's what we call a Bad Thing (tm). I agree on indenting though. Always use tabs. NEVER use spaces. *shakes an angry fist at coding n00bs* Tabs allow a programmer to set the spacing to his preference without changing the code. Spaces force the look of however many spaces there are in any editor, and really screws up a lot of formatting. Any editor worth its salt should adjust the tabs you create without incident, but it's much more difficult to handle old spaces you've typed, you communist. Gligh! It makes it look more like Perl. That’s what we call a Bad Thing ™.

I agree on indenting though. Always use tabs. NEVER use spaces. *shakes an angry fist at coding n00bs* Tabs allow a programmer to set the spacing to his preference without changing the code. Spaces force the look of however many spaces there are in any editor, and really screws up a lot of formatting. Any editor worth its salt should adjust the tabs you create without incident, but it’s much more difficult to handle old spaces you’ve typed, you communist.

]]>