...and your proposal is great, it looks very promising! > A. Configuration problems should a be separate errorspace (at the time of > initialization): > 0. Success > 1. invalid command line options > 2. no 1-wire source (bus master) specified > 3. no 1-wire source (bus master) available > 4. insufficient permission from operating system > 99. Unknown error perfect!
> B. Closing should be a separate errorspace It could overlap with opening errorspace > 0. Success > 99. Unknown error 5. no device/bus-master initialized, can't close > (D) Read and (C)Directory should be a combined errorspace (because "get" > can > be either) and we might as well combine (E)Write since there is > considerable > overlap: > 0. Success > 1. Uninitialized > 2. Directory (not appropriate) What does it mean? Maybe in case a read is done from a directory? > 3. Not a directory (not appropriate) What does is mean? Maybe in case a get is made from an device attribute?? > 4. Read not supported > 5. Write not supported > 6. Read-only What is the difference to 4. Read not supported? > 7. Invalid path Great, this is very helpful!!! > 8. Invalid device (CRC wrong) > 9. Invalid device (alias error?) In case a device name is clearly found as clias (so no f.i.c or similiar notation), but it is not listed in the alias file? > 10. Bus does not exist > 11. Bus is not working > 12 Bus is wrong type What is this??? > 13 Bus short Great, but isn't there a big overlap with "11. Bus is not working"? Of course, if you are able to distinguish between shorted and "not working" that would be great! > 14. Not an array > 15. Array out of bounds For example in case a <DS2408>.PIO.ALL writes 9 values (more as the max 8 possible) - great!!! What to do if only 7 values are give, can this also be detected? > 16. Not a scalar > 17. Not a bitfield > 18. 1-wire error What is this? > 99. Unknown error Which error will be returned, in case a 1-Wire device is simply not available at the moment? So if it was unplugged, the cable is broken, got lost or somehow destroyed? I would propose something like "19. not reachable" the application will then retry endless, because it could happen that the device appears again. BTW: In this case it also makes sense to look again into the alias text file, because it could happen that the device (with the same alias name) is replaced by a new one (with a different unique id) Achim -- View this message in context: http://old.nabble.com/errno-in-owcapi-tp32275960p32300929.html Sent from the OWFS - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
