Re: [Sdcc-user] documentation & open source generally

[Philipp K. K. <pk...@sp...>]

Richard Erlacher schrieb:

> Do you program to a set of requirements, or do you simply imagine what you 
> want to write and then, when you think you've finished, accept what you 
> have, regardless of what it does?  How do you know that you've done what you 
> set out to do?  In fact, how do you know you've finished?  After that, how 
> do you verify that it works as it should?  There's a huge difference between 
> trial and testing, doncha know!

When we work on sdcc and want to make an improvement we usually have bug
reports and feature requests (if we want to do something new we open
them, note feature is a broad term here and could include anything
that's not a bug to be fixed including code cleanup, etc). When we've
implemented it we close the bug report /feature request.
When I try to implement something bigger I split it up into multiple
feature requests / bug reports and make a Wiki page for it (see
http://sdcc.wiki.sourceforge.net/Philipp%27s+TODO+list for my effort to
reduce the size of the generated code in the Z80 port).

For other projects (I use sdcc for games) it's less formal, with
scetches on paper and I will make changes that I never thought about at
the start. When it's finished (or I think there won't be any further
fundamental changes in the gameplay) I write a short manual.

Philipp