Req #7766 [Opn->Bgs]: Reference to '1TBS' confusing

From: Date: Sat, 03 Jun 2006 17:05:08 +0000
Subject: Req #7766 [Opn->Bgs]: Reference to '1TBS' confusing
References: 1  Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-7986@lists.php.net to get a copy of this message
Edit report at http://pear.php.net/bugs/bug.php?id=7766&edit=1 ID: 7766 User updated by: dominics at gmail dot com Reported By: dominics at gmail dot com -Status: Open +Status: Bogus Id: 7766 Type: Feature/Change Request Package: Documentation PHP Version: Irrelevant New Comment: Whoops. Ignore me. Please. Previous Comments: ------------------------------------------------------------------------ [2006-05-30 23:29:52] dominics at gmail dot com Description: ------------ http://pear.php.net/manual/en/standards.funcdef.php makes a reference to the 'One True Brace Style'. I think this reference is at best confusing and at worst contradictory to the example given. What I mean is that in every non-PHP resource I've been able to find, 1TBS refers to the style used by Kernighan and Ritchie ('K&R' style) - this is the style the Unix kernels are written in ('Kernel' style). The style used by PEAR would be commonly known as the 'BSD' or 'Allman' style. I'm not looking to start a holy war about brace style. I do, however, think that we should be clear about exactly which brace style PEAR uses, and, regardless of what 1TBS is understood to stand for, it is an ambiguous term - it means a different thing to someone coming from C. Wikipedia is a good reference for the indent style terminology listed above: http://en.wikipedia.org/wiki/One_True_Brace Expected result: ---------------- Function declarations follow the 'BSD' or 'Allman' convention: Actual result: -------------- Function declarations follow the "one true brace" convention: ------------------------------------------------------------------------ -- Edit this bug report at http://pear.php.net/bugs/bug.php?id=7766&edit=1

« previous php.pear.doc (#7986) next »