> As part of my continuing mission to break all Mirage APIs, I've > written up some thoughts on how to improve error handling: > > https://github.com/mirage/mirage-www/pull/274
I'm still like proposition 5 very much, so I've started to see what it could look like in practice: https://github.com/mirage/mirage/pull/383 My plan is to adapt the various libraries needed to run mirage-skeleton on top of this. I think it will not be too much painful, mainly because the removal of DEVICE.connect means that there is no more DEVICE.id and DEVICE.error to care about. I'll keep the list updated on the progress. While doing this, I've also cleaned up V1 documentation and updated it online: http://mirage.github.io/mirage/V1.html Thomas > > Although written as if it's a final design, it's intended only as a > starting point for discussion, to find out what we do and don't agree > on. Please add comments, information about successful approaches > you've seen, etc. > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
