Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of igorcosta@gmail.com
 designates 209.85.220.175 as permitted sender)
Received-SPF: pass (google.com: domain of igorcosta@gmail.com designates
 10.52.28.167 as permitted sender) client-ip=10.52.28.167;
MIME-Version: 1.0
In-Reply-To: <6AD759E6-E8A8-45E0-B589-09CCF1073C6B@classsoftware.com>
References: <CB707750.3CAA4%aharui@adobe.com>
 <4F4B5506.2050305@leichtgewicht.at>
 <6AD759E6-E8A8-45E0-B589-09CCF1073C6B@classsoftware.com>
From: Igor Costa <igorcosta@gmail.com>
Date: Mon, 27 Feb 2012 09:55:03 -0300
Message-ID: 
 <CAPxxvdkDg0dL55XRTdyjEmuJ9JvOWo8-3Q4ttnY=w1vf-mqjWA@mail.gmail.com>
Subject: Re: Code formatting for patch submissions
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf3079b95ea575d604b9f19f45

--20cf3079b95ea575d604b9f19f45
Content-Type: text/plain; charset=UTF-8

This has been discussed in mailing list before.

I guess this is more related to personal style of coding than overall style.

To myself, the current way of Adobe code styles fits on our needs, we need
to focus on concrete changes, not substantial ones.

Writing a guide to help new contributors is much better than change hole
code way of style.

Like theses does here
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions and
here
http://www.dclick.com.br/2007/02/13/adobe_flex_coding_guidelines_english/


Regards
----------------------------
Igor Costa


On Mon, Feb 27, 2012 at 8:34 AM, Justin Mclean <justin@classsoftware.com>wrote:

> Hi,
>
> I suggest we take the pragmatic path in that we take how the current code
> is formatted. Constancy make it easier to work on the code. I'm sure on
> occasion there will be valid reason for breaking those rules and over time
> we may move to a new set of rules.
>
> Thanks,
> Justin

--20cf3079b95ea575d604b9f19f45--