Re: sets for sequence.e?

new topic     » goto parent     » topic index » view thread      » older message » newer message

CChris wrote:
> 
> 
> Done, though I may wish to add a few more unit tests. As usual, the tests
> themselves
> had way more problems than the code they tested.

That may be but it's vital that unit tests exist, for instance, it caught quite
a bit last change. One function was changed, and that function was tested with a
sample app and it worked. However, all the other functions that relied upon the
changed function began to fail.
 
> There is no .htx documentation yet, but it is in sets.e and would simply need
> to move from here to there with some format tags. I'm not sure I have time to
> do that next week (53 entries).

Really? 53 new functions?

> What's best?

Please put a 

-- TODO: document

At the beginning of each function that is a global and then commit. Before
functions go into SVN, they should be unit tested, however, not necessarily
documented. But, we must have an easy way to see which ones are not documented.
An undocumented function is one that does not exist to the public.

--
Jeremy Cowgar
http://jeremy.cowgar.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu