News for hackers. Stuff that matters.
Re:Rewrite Linux Kernel in Rust? by vog on Sunday June 04, 2017 @08:33AM (#14481184)
> C code compiles fine after decades

Early C code doesn't compile on modern systems at all.

Speaking of early C code, every vendor had their own version. C standardization had to go a long way.

Even today, writing portable C code is hard. Need a portable 128-bit integer? Good luck on Windows. Need a portable 32-bit integer? Better take a C implementation that provides int32_t, because just using "int" bites you when switching from 32-bit to 64-bit platforms.

Oh, and int32_t was introduced in C99, which is not exactly "decades" ago, but admittedly that was 18 years ago. However, I wouldn't bet on portability of any code older than that, unless the authors of that C code were extremely careful and anticipatory. But then, with enough effort (and perhaps code generation), you can create portable code in any language.

Rust skips all that mess, by having a clear experimental phase in the 0.x versions. It became stable with a clear commitment to backwards compatibility since 1.0, which was released in 2015.

Re:Rewrite Linux Kernel in Rust? by tom_mellior on Sunday June 04, 2017 @06:12PM (#14483907)
> Need a portable 32-bit integer? Better take a C implementation that provides int32_t, because just using "int" bites you when switching from 32-bit to 64-bit platforms.

Citation needed. Which compilers for which machines are you talking about? I don't think any change the size of int. What does break is the assumption that int is the same size as pointers, but that's because the sizes of pointers change.

Re:Rewrite Linux Kernel in Rust? by vog on Monday June 05, 2017 @05:22AM (#14486262)
Whoops. I meant 16-bit versus 32-bit integers, when switching from 16-bit to 32-bit systems. Sorry for the confusion. Fortunately, they didn't repeat that mess for 32/64 bits, at least not for integers, but "decades old code" is still affected.
Re:Rewrite Linux Kernel in Rust? by tom_mellior on Monday June 05, 2017 @05:54AM (#14486354)
Ah, yes. I agree, that was a mess!