move all unix compatibility layers to shared Unix lib
Jan Rinze (235) 368 posts |
Hi all, after a discussion with Ben Avison it has come to my attention that there are modules that have their own UNIX compatibility layer. Specifically when it comes to time keeping and such. It would be i.m.h.o. a nice improvement if these were transferred to a single module. Most likely that is already available but for example both Internet and the USB module have their own implementation of signals and getting accurate time. They both need the same calls.. Each implementation has its own peculiarities but somehow it should be possible to make a single implementation that works well for both (and the ones i have not found yet). Regards, Jan Rinze. |
Peter Naulls (143) 147 posts |
Yes, good. But also a slippery slope ;-) Let’s see if I can cover everything:
There’s a lot to be said for having a Unix compatibility layer within RISC OS - indeed, it already has some of that – and code duplication is to be avoided if possible. What I want to suggest is avoiding improving this RISC OS layer, when UnixLib already provides considerable functionality in this area. I appreciate also that this is a hard problem – UnixLib is not really suited to being a module (and will definitely need some work to built with Norcroft). So, not really a recommendation, just some observations. In terms of practicalities, it may just be best to continue down the path implied by Jan. |