Re: AW: [PEAR] I can't believe it...
| From: | Markus Fischer | Date: | Fri, 23 Nov 2001 10:58:03 +0000 |
| Subject: | Re: AW: [PEAR] I can't believe it... | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-534@lists.php.net to get a copy of this message | ||
On Fri, Nov 23, 2001 at 10:13:31AM +0000, Conor Kerr wrote :
> The only last point I would make is from a different perspective... can
> anyone say *why* spaces are better to use than tabs given that the tab
> width can be set in almost every editor to an equal setting?
Spaces:
They show the same code whereever used (also very good
for presentations).
You don't run into ugly looking / missformated code when
someone breaks the code lines and indents the next line:
| function foo($param1, $param2, $param3, $param4,
| $param5, $param6
If I would have used TABS here, it would look
missformated. This would even be true for mail clients if
they don't use 4 spaces to display a TAB for this
example.
Tabs:
Can be easier adjusted to fit the users preference and
they're less characters (well, if that important? not to
me).
(Hm, anymore suggestions?)
I'm also using TAB and also thought 'Oh my God, why does PEAR
use Spaces?'. But since my editor (vim) handles them
transparently (its very nice to specify editor modes in
sources files with :vim <options:, same for emacs) it was ok
with me.
Let's put it this way: I' flexible and adjust to other
preferences without loosing mine. I'm now editing code files
some with TABs, some with SPACES and until I set the 'list'
option in my editor I won't even notice.
2c from Markus