Re: Compiler implementation language preference ?

steve kargl <sgk@REMOVEtroutmask.apl.washington.edu>
Wed, 19 Dec 2018 23:19:04 -0000 (UTC)

          From comp.compilers
Related articles
[5 earlier articles]
Re: Compiler implementation language preference ? 157-073-9834@kylheku.com (Kaz Kylheku) (2018-11-10)
Re: Compiler implementation language preference ? 157-073-9834@kylheku.com (Kaz Kylheku) (2018-11-10)
Re: Compiler implementation language preference ? portempa@aon.at (Richard) (2018-11-10)
Re: Compiler implementation language preference ? walter@bytecraft.com (Walter Banks) (2018-11-10)
Re: Compiler implementation language preference ? ibeam2000@gmail.com (Nick) (2018-11-13)
Re: Compiler implementation language preference ? aaronngray@gmail.com (Aaron Gray) (2018-12-19)
Re: Compiler implementation language preference ? sgk@REMOVEtroutmask.apl.washington.edu (steve kargl) (2018-12-19)
Re: Compiler implementation language preference ? martin@gkc.org.uk (Martin Ward) (2018-12-20)
Re: Compiler implementation language preference ? aaronngray@gmail.com (Aaron Gray) (2018-12-21)
Re: Compiler implementation language preference ? 157-073-9834@kylheku.com (Kaz Kylheku) (2018-12-21)
| List of all articles for this month |
From: steve kargl <sgk@REMOVEtroutmask.apl.washington.edu>
Newsgroups: comp.compilers
Date: Wed, 19 Dec 2018 23:19:04 -0000 (UTC)
Organization: A noiseless patient Spider
References: 18-05-009 18-12-007
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

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]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.