[PEPr] +1 for System::System_Serial

Justin Patrin (http://pear.php.net/user/justinpatrin) has voted +1 on the pr
oposal for System::System_Serial.

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=149
Vote information:
http://pear.php.net/pepr/pepr-vote-...le=justinpatrin

This vote is conditional. The condition is:

Strings should use ', not " if they have no replacements within them (backsl
ash expressions like \n or variables). It requires slightly less parsing and
 makes it clear that the string is literal.

Comments should be tabbed according to CS. If there is nothing in CS specifi
cally about this, the / should be level with the code it's commenting, the *
 should be one more space in as should the */. Like this:

/**
*
*/
function foo() {
}

NULL should be null (I believe)

Function definitions should use the one true brace style:

function ($arg)
{
//code
}

--
Sent by PEPr, the automatic proposal system at http://pear.php.net

On 1 Oct 2004 17:31:28 -0000, Justin Patrin <papercrane@reversefold.com> wrote:
>
> Justin Patrin (http://pear.php.net/user/justinpatrin) has voted +1 on the 
proposal for System::System_Serial.
>
> Proposal information:
> http://pear.php.net/pepr/pepr-proposal-show.php?id=149
> Vote information:
> http://pear.php.net/pepr/pepr-vote-...le=justinpatrin
>
> This vote is conditional. The condition is:
>
> Strings should use ', not " if they have no replacements within them (back
slash expressions like \n or variables). It requires slightly less parsing a
nd makes it clear that the string is literal.
>
> Comments should be tabbed according to CS. If there is nothing in CS speci
fically about this, the / should be level with the code it's commenting, the
 * should be one more space in as should the */. Like this:
>
>     /**
>
>      *
>
>      */
>
>     function foo() {
>
>     }
>
> NULL should be null (I believe)
>
> Function definitions should use the one true brace style:
>
> function ($arg)
>
> {
>
>     //code
>
> }
>

Please ignore the extra newlines. Is this a Pepr bug?


--
paperCrane --Justin Patrin--