Date: Mon, 31 Dec 2018 10:19:26 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Diane Bruce <db@db.net> Cc: Enji Cooper <yaneurabeya@gmail.com>, Eric McCorkle <eric@metricspace.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Speculative: Rust for base system components Message-ID: <20181231181926.GA2497@troutmask.apl.washington.edu> In-Reply-To: <20181231180524.GA2522@night.db.net> References: <ca76e5f7-6e59-bd67-144a-90ad66f0252e@metricspace.net> <CANCZdfrMY73-7vK6F6q-iPdW7EOUP8CPThkyxwOoOWedyMu5Ag@mail.gmail.com> <713BA6E4-1C4E-4890-831F-6379D3AB4425@gmail.com> <20181231180524.GA2522@night.db.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 31, 2018 at 01:05:24PM -0500, Diane Bruce wrote: > On Mon, Dec 31, 2018 at 09:36:18AM -0800, Enji Cooper wrote: > > > > > On Dec 31, 2018, at 7:02 AM, Warner Losh <imp@bsdimp.com> wrote: > > > ... > > <offtopic> > > At the end of the day, I think the key is that the FreeBSD project needs to start expressing more complicated subsystems in terms of OOP languages, like C++, Rust, etc, instead of expressing most of the code in C. I do think (for instance) a service management system would be a good candidate for modern C++ or Rust. > > </offtopic> > > Well, as someone who remembers when Fortran was King and much systems(!) > programming such as editors etc. was done in Fortran, I cheer on > any effort moving on from the failed Fortran compiler 'C'. > All those Fortran codes from years ago, if written in standard conforming Fortran, will still compile today. J3 (Fortran standardization committee) goes to great length to retain backwards compatiability with older standards. The latest revision to the language was ratified as an international standard only a few weeks ago. https://wg5-fortran.org/f2018.html -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181231181926.GA2497>