On 2010-09-13 23:46, Simo Sorce wrote:
On Mon, 13 Sep 2010 17:02:19 -0400
Adam Young wrote:
The is a really nasty bug that the "same line" policy avoids.
Javascript often attempts to guess where you meant to put semicolons,
and puts the in for you, without telling you.
return
{
status:
On Mon, 13 Sep 2010 17:02:19 -0400
Adam Young wrote:
> The is a really nasty bug that the "same line" policy avoids.
> Javascript often attempts to guess where you meant to put semicolons,
> and puts the in for you, without telling you.
>
> return
> {
> status: true;
> };
>
>
> actual
On 09/13/2010 04:49 PM, Simo Sorce wrote:
On Mon, 13 Sep 2010 11:44:53 -0400
Adam Young wrote:
I've updated the page. Bascially, I took the python coding standards
and aaplied them to our code. THis seems to be the path of least
resistance.
People used to Camel case will have to get use
On Mon, 13 Sep 2010 11:44:53 -0400
Adam Young wrote:
> I've updated the page. Bascially, I took the python coding standards
> and aaplied them to our code. THis seems to be the path of least
> resistance.
>
> People used to Camel case will have to get used to underscores
>
> People used to
On 09/13/2010 03:33 PM, Endi Sukma Dewata wrote:
Hi Adam,
- "Adam Young" wrote:
https://fedorahosted.org/freeipa/wiki/Javascript_Coding_Standards
Whitespace: Do we put a space in function definition between the () and {}?
function(){...}
vs.
function() {...}
Or does it mat
Hi Adam,
- "Adam Young" wrote:
> https://fedorahosted.org/freeipa/wiki/Javascript_Coding_Standards
Whitespace: Do we put a space in function definition between the () and {}?
function(){...}
vs.
function() {...}
Or does it matter?
Compound statement: This is probably Python syntax.
if f
I've updated the page. Bascially, I took the python coding standards
and aaplied them to our code. THis seems to be the path of least
resistance.
People used to Camel case will have to get used to underscores
People used to putting underscores before private variables will go
through withdr
