Re: ugen test-level status in doc?
Date | 1999-09-05 02:53 |
From | Larry Troxler |
Subject | Re: ugen test-level status in doc? |
David Boothe wrote: > > Larry Troxler: > >Actually, my idea wasn't just to document known errors, but to >document > >known non-errors, IOW to document that someone somewhere is >sucessfully > >using a certain ugen, so that someone can feel confident in using > > Why not just assume they all work, until you find out otherwise, either > through the list or by personal experience? I realize that can be > frustrating, but that's why the list exists. > Well, given my admittedly limited experience so far, this assumption is not warranted! If I had an infinite amount of available time, it wouldn't matter. But given an hour per evening, it becomes quite a problem. Am I the only one on this list with a day job? > In some cases, what appears to be a bug may only be a lack of understanding > about what the opcode is supposed to do. Often this is due to unclear > documentation - a situation I am always trying to improve. (More about that > later) > In some cases, yes, but not in most cases (IMHO). Larry Troxler |
Date | 1999-09-05 20:09 |
From | tolve |
Subject | Re: ugen test-level status in doc? |
think somewhere along the way i was misinterpreted: never meant to suggest absolutely anyone should be able to add information to a database regarding known bugs -only multiple contributors given such access. all others simply view. also, as mentioned, though i'm willing to set up structure of such a database, it would be quite a bit of work for others to maintain the information. do believe that at least a simple known bugs list would be useful. certainly it is not that bizarre a concept in this world. but how about this least possible work solution for a start: mr ffitch declares international csound bug week at his convenience. all users are invited to blitz the list with bugs they have encountered with "international csound bug week" in the heading. *all such bugs must have been in some way confirmed on this list and should not currently be listed as solved in the most recent official ffitch communiques* (posts of new bugs could and should of course continue to be posted but without the international csound bug week moniker in the subject heading) users would be free to set up a filter to sort international csound bug week posts for reference. viola! this process could be repeated any time the manual is being updated. tolve |