02-23-2010, 05:09 PM
So far, it's looking good.
I've updated the buglist, and it's almost all green now.
The more I think about it, the more I'm thinking that if you make the "library list" page in the wiki, that it would be as well to put any additions in there. Then people can use them as and when they will, and they are better documented. We could add a standard set - I'm working my way towards a math library, for example - into the pile, but the wiki section will be at least as important, since it documents what all this stuff does. On more than one occasion I've found myself writing code that would be as easy to do with an import from the library that's already there.
One problem with things like the math library is are people looking for speed or size? Often it's a trade between the two. You either get big, or slow - or something in between. It might be easier to have a fully documented method or two there, and explain how it came about and then people can choose to spend bytes or not by modifying the routines.
I've updated the buglist, and it's almost all green now.
The more I think about it, the more I'm thinking that if you make the "library list" page in the wiki, that it would be as well to put any additions in there. Then people can use them as and when they will, and they are better documented. We could add a standard set - I'm working my way towards a math library, for example - into the pile, but the wiki section will be at least as important, since it documents what all this stuff does. On more than one occasion I've found myself writing code that would be as easy to do with an import from the library that's already there.
One problem with things like the math library is are people looking for speed or size? Often it's a trade between the two. You either get big, or slow - or something in between. It might be easier to have a fully documented method or two there, and explain how it came about and then people can choose to spend bytes or not by modifying the routines.