Date: Sat, 16 Feb 2002 13:45:27 -0700 From: Brett Glass <brett@lariat.org> To: aw1@stade.co.uk, "freebsd-chat@FreeBSD.ORG" <freebsd-chat@FreeBSD.ORG> Subject: Re: Fortran (was Re: Why is Python slower on FreeBSD than Windows?) Message-ID: <4.3.2.7.2.20020216134025.01cfd980@localhost> In-Reply-To: <20020216022307.B79138@titus.hanley.stade.co.uk> References: <20020215145841.O33755-100000@resnet.uoregon.edu> <3C6D22C2.268E6915@pythonemproject.com> <20020215145841.O33755-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:23 PM 2/15/2002, Adrian Wontroba wrote: >"Real Programmers can write Fortran in any language." To quote from an >old, and quite funny, list of things that Real Programmers do and don't >do. > >It was my first language. Fortunately I was soon introduced to Algol. Funny thing about Algol: When Algol-60 (which had some features that neither FORTRAN nor C has, such as range and bounds checking) for UNIVAC hardware was completed, scientists at Case Institute of Technology (where I did my undergraduate degree) ported some old government code over and tried to run it. The machine immediately reported runtime errors. Variables were undefined; subscripts were going out of bounds; the results that were produced if the errors were ignored were virtually random. And now the punch line: the code they'd ported had been used in the design of nuclear weapons. I trust neither FORTRAN nor C to this day. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20020216134025.01cfd980>