Open
Description
There is a lot of discussions already about it, I'd expect more, so maybe we can make a place for it (to list, brainstorm and set directions).
Some ideas to (eventually) consider (please update as needed):
file / directory APIs(done)a standard style to implement?changes vs. wrappersissues: fopen() like API for adfFileOpen() #38, Things to finish for 0.8.0 #40
consistent naming (ie. submodule prefixes) across the library(done)isolating client API from internal one (separated headers in(mostly done, but may be improved)include/
?)eg. for file API, expose only a wrapper over the low level functions(?)
devices(done)allow more types of devices (not only one native and "dump"), also custom, user-implementedadd a memory/ramdisk device - useful ie. for testing (see the comment belowunify the device interface for all typesthe type of the device is currently is set inadfOpenDev()
and depend on the name (ie filename) of the deviceinstead: differentiate opening/creating depending on type (need rather different functions as different arguments are needed, eg. filename for dump, size for ramdisk device)
make the same device structure with interface also for dump devices
- review error codes (see the comment below) and their use (partially done, can be improved)
- reduce amount of (or remove completely) string output to stdout/err (or leave if a "logger" defined/enabled)
- replace output warnings with proper return codes
- bitfield vs enumeration
- bitfield would allow to aggregate more than one in single return code
- that was the orig. idea (there is even a test
hasRC()
- but it is not used anywhere...)
- bitfield vs enumeration
- user readable (string) error info: logger vs errno/last error info
errno
/last error info- only static error string or dynamic (that would include more info like filename, block
number or other data relevant for the error) - drawbacks: single, global (what can be problematic, even though the lib is not supporting multi-threading)
- only static error string or dynamic (that would include more info like filename, block
- use logger for more detailed error info (if logger enabled/defined)?
Each of these might be a separated issue (or even issues), that could be linked here (so that it is easier to navigate).
Metadata
Metadata
Assignees
Labels
No labels