Re: RFC: coding standards document

Andi, I find that relying on tabs is a bad idea, since the default tab width varies from editor to editor. We just had the same discussion on this list, and the consensus was to not use tabs. - Stig On Sat, 16 Dec 2000, Andi Gutmans wrote: | Shouldn't the indentation of PEAR be the same as of PHP? | A tab "represents" four spaces but we don't do a tab->spaces conversion but | keep them as tabs. | | Andi | | At 01:18 AM 12/16/00 +0200, Martin Pedak wrote: | >Chuck Hagenbuch wrote: | > | >>Quoting Martin Pedak <qwerty@webmedia.ee>: | >> | >>>What is what? | >>>http://utvikler.start.no/code/php_coding_standard.htm and the | >>>attachented CODING_STANDARS.txt | > | >>The attached file is just a link (broken, it seems) to some company's | >>standard | > | >Sorry, put the "l" (L) to the end of the URL and it works. (Copy & Paste :)) | >http://utvikler.start.no/code/php_coding_standard.html | > | >Martin Pedak | > | > | >-- | >PHP Extension and Add-on Repository (PEAR) mailing list. | >Documentation can be found at http://pear.php.net/doc/pear.html | >To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the | >mail address you subscribed with. | | --- | Andi Gutmans <andi@zend.com> | http://www.zend.com/ | |