Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: steve kargl Newsgroups: comp.compilers Subject: Re: Compiler implementation language preference ? Date: Wed, 19 Dec 2018 23:19:04 -0000 (UTC) Organization: A noiseless patient Spider Lines: 17 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <18-12-008@comp.compilers> References: <18-05-009@comp.compilers> <18-12-007@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="74762"; mail-complaints-to="abuse@iecc.com" Keywords: Fortran, history, comment Posted-Date: 19 Dec 2018 20:15:51 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2136 Aaron Gray wrote: > On Tuesday, 22 May 2018 18:39:07 UTC+1, Michael Justice wrote: >> Is there any preference to writing a compiler in say c instead of say >> java, fortran, basic etc? ... > >> [Mostly people use what they're used to, or in languages that are easy >> to bootstrap on the machines they want to use. IBM's Fortran H >> compiler was famously written in itself, but I wouldn't write a new >> compiler in Fortran because it doesn't have great data structuring or >> dynamic storage management. (Yes, I know that Fortran 2008 is a lot >> different from Fortran 66.) -John] The latest Fortran standard is informally referred to as F2018. It became the official standard a week or so ago. https://wg5-fortran.org/f2018.html [You're right, but I still wouldn't want to write a compiler in it. That's not what it's for. -John]