Chris's Wiki :: blog/linux/PortingKernelCodeChallenging Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/PortingKernelCodeChallenging?atomcommentsDWiki2018-08-29T05:49:58ZRecent comments in Chris's Wiki :: blog/linux/PortingKernelCodeChallenging.By Someone from Belgium on /blog/linux/PortingKernelCodeChallengingtag:CSpace:blog/linux/PortingKernelCodeChallenging:b9d8d2c322940f6a98953975c2fc94a5b29ae41cSomeone from Belgium<div class="wikitext"><p>Maybe I’m oversimplifying this, but coming from a strongly typed background (Haskell) makes this error system seem completely unmaintainable to me. I understand that this is at a very low level and in C. In a statically typed language, you’d have typed errors.</p>
</div>2018-08-29T05:49:58ZBy Some random guy on /blog/linux/PortingKernelCodeChallengingtag:CSpace:blog/linux/PortingKernelCodeChallenging:0078e3cf122c5d4e542671d16b03e91fb439a9c3Some random guy<div class="wikitext"><p>This is a great description of a complex problem in the "seam" between two complex systems. I suggest it be added to the read me files on that particular piece of the zfs code base</p>
<p>Would be interesting to hear more about converting code to use Linux kennel primitives</p>
</div>2018-08-28T17:46:56Z