Hello Jaroslav! Nice to see someone working on this, and thanks for linking in the ML. I can help answer some of the questions.
The state of HelenOS libc and libposix is far from ideal, and it's going to keep evolving in the coming months. Ideally, libc should eventually be compatible with C and C++ standard (if not outright compliant), and at the very least not have outright conflicts with the POSIX standard. Insofar as a subset of C++ library can be viewed as a wrapper for C library, I think it would be adequate for that subset's completeness to match what's implemented in libc and/or libposix. If you think a part of C standard library is needed for your work to be successful, it should be implemented in libc first (and I'll be happy to review and possibly integrate your work). When it comes to particular implementation, I'd personally prefer LLVM's libc++. You should refrain from using GPL-licenced code, but BSD and MIT are fair game (so long as you follow their requirements). I'm not entirely sure about Apache. Also, this page might come in handy: https://clang.llvm.org/docs/Toolchain.html It's in the best interest of maintainability to keep changes from upstream code to a minimum. For example, conditional sections should not be removed unless it's necessary, and it might be better to provide pthreads API implemented using fibrils, than to change the caller directly. Currently, libposix has empty stubs for pthread API, but having a fibril-backed libpthread as a separate library is something I'd like to have. For compiler support, I'm currently reviving clang (see my latest commits to mainline), so if possible, you should strive to support cross-gcc and clang. You can safely ignore everything else. Last, but not least, I'm available most afternoons/evenings on our IRC channel, so I invite you to pop in anytime and ask any questions. My nickname on IRC is jzr. -- jzr On 10 October 2017 at 16:06, Jaroslav Jindrák <[email protected]> wrote: > Hi Martin, > > I'm sending you a research/progress file I've written so far that documents > my progress. > It includes information on the things I have already done, possible porting > sources, discussion > of the portability of the different modules (i.e. standard headers) and > section 6 contains a few > questions I wanted to ask you (mostly regarding the direction you'd like > this thesis to take - if you > do have preference). > > PS. Since HelenOS is a community project, I decided to CC the helenos-devel > mailing list in the > case somebody else would be interested (or would want to voice their > preference in the matters > discussed). (Although I'm not sure how that'd be incorporated into the > thesis.) > > If you prefer to meet in person to discuss this, let me know and I'll come > to MS. > > S pozdravem, > Jaroslav Jindrak > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
