Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Flex SDK code conventions
From: Jun Heider <jun@realeyes.com>
In-Reply-To: <CB2BA03F.5082%cframpto@adobe.com>
Date: Thu, 5 Jan 2012 16:59:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F19C80D4-CE87-4324-8822-D01E87E9D14B@realeyes.com>
References: <CB2BA03F.5082%cframpto@adobe.com>
To: flex-dev@incubator.apache.org


On Jan 5, 2012, at 4:54 PM, Carol Frampton wrote:

> I think it would be okay to move the Flex coding standard over to =
Apache.

That would be awesome!

>=20
> We/I updated the standard about a year ago with some changes people
> wanted, like allowing line lengths up to 100 chars.  We didn't take =
the
> time to eliminate all the TBDs.
>=20
> I will strongly advocate for 4 spaces rather than tabs.  Too many apps
> mess up the tabs or use 8 spaces rather than 4 by default.

That makes sense.  If there's a good argument, if this seems to be, I'm =
fine with spaces.

>=20
> I'm not sure I want to see existing code reformatted because it gets =
very
> hard to go back to earlier revisions and see what changed.

Completely onboard with NOT reformatting for this very reason.