Executive Summary for Libraries
Please could you add an "Executive Summary" for each of your bolt-on libraries.
What I would hope to see is:
What it will support (e.g. for Mass-Storage library, will it only do FAT32 or will it also support FAT12, FAT16, exFAT; Long Filenames. IPV4 and/or IPV6)
What system resources (RAM) are suggested for minimum/typical/high-performance builds.
Optional features e.g. write-back cache, multi-thread support; can a file be open simultaneously for appending and reading?
I do have a need for TCP/IP support soon, but I don't want to have to learn your library only to reject it because (for example) it only targets too low-end applications that don't care about throughput. Yes I will be learning TCP/IP at the same time, and yes I have bought Vols 1 and 3 of TCP/IP illustrated.
I was surprised how difficult it is to find out what your "fixed-point" library was intended for. Yes it might eventually provide more general fixed-point support, but if at the moment all it does is aid e.g. GPS calculations then please say that!
Please sign in to leave a comment.
Comments
0 comments