From mint-bounce@lists.fishpool.fi Sat Jul 17 04:47:08 2010 Message-ID: <4C416DBE.8090902@online.no> Date: Sat, 17 Jul 2010 10:45:50 +0200 From: Jo Even Skarstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Bit-Depth and Graphics stuff.... References: <4C34C2E4.5080909@online.no> <3847624A-0252-410C-B103-5BA7AAE195E0@gmail.com> <20100708223029.A20680@mbernstein.de> <47B6FCDC-13AA-4B15-BF8B-2A59E6E9991F@gmail.com> <20100711114630.B16224@mbernstein.de> <20100714213300.A17990@mbernstein.de> <4D2B7F5C-46D9-4C76-847F-FCC7E2CA633E@gmail.com> <1F316BAC-66EA-4E12-90ED-27F5D2D713FC@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 07/17/2010 04:47 AM, Paul Wratt wrote: > On API proposals, I hark back to the use of wiki in making them > available in a permanent form (as opposed to the list or a text file), A wiki is a poor tool for this. API docs (even for unimplemented stuff) belongs in the source of the AES itself (or perhaps in the bindings, but ideally the bindings should be automatically created from the source too), so it can easily be extracted during the build process. It's the only way to make sure that the docs are up to date. Keeping docs and sources separate means that the docs simply won't be updated - this is how programmers work ;-) Jo Even