Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: asdoc comments for flash player and SDK version numbers
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: 
 <CAEFz_vvpmjS39=PucMp9RphuPdBdCN4f30DqEAEJ4eMHN3VgiA@mail.gmail.com>
Date: Thu, 16 Feb 2012 20:32:07 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEF5D538-DD75-4F2D-8677-3B539A6C1884@classsoftware.com>
References: <FA124D97-2584-41D4-A96D-F93293F0F8B4@classsoftware.com>
 <1329381498.4139.10.camel@lapsang>
 <435062CE-006D-4E52-B4B8-F9F68E1F3E37@classsoftware.com>
 <CAEFz_vvpmjS39=PucMp9RphuPdBdCN4f30DqEAEJ4eMHN3VgiA@mail.gmail.com>
To: flex-dev@incubator.apache.org

Hi,

> I'm not quire sure what you mean. The ideal solution would be to =
figure out
> a way to keep comments in such a way that the during development =
they're
> not in our files but at release or at patch submission the proper
> documentation is there.
Yep exactly what I was suggesting. Use a script to strip out unwanted =
comments once code is checked out. Work on those files but when =
submitting patches missing comments are ignored or added back in when =
committing to SVN. Don't know exactly how you would do that - probably =
not easily possible. Moving the comment out to separate files is =
probably simpler (and modifying the documentation generation process) =
but as someone else said that would make it harder to keep code and docs =
in sync.

Justin