From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Mariner 1 / FORTRAN bug
Date: Fri, 09 Aug 2019 15:03:16 -0700
Organization: A noiseless patient Spider
Message-ID: <871rxuq9nf.fsf@nightsong.com>
References: <1992Dec4.141816.1@happy.colorado.edu>
	<86986725-f34e-46d7-9efc-d15d94379048@googlegroups.com>
	<qihm04$h5a$1@dont-email.me>
	<97509e4d-05b9-4b6a-ab12-613abbe562b0@googlegroups.com>
	<qij3pe$3m5$1@dont-email.me>
	<011db4d7-3455-407d-9a1d-aa747d35c538@googlegroups.com>
	<qijvs9$11g4$1@gioia.aioe.org>
	<67d7dee5-d2d0-4569-8358-36d2fad4cf0f@googlegroups.com>
	<9f203010-2432-4ff6-a44c-3ecde392ff12@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org;
 posting-host="4b1b438d0dc83d977280847fd831f336";
	logging-data="16976"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+FCTtvo4zd4Sz0OaIkz0cN"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Cancel-Lock: sha1:uGPLKBkf4hVCsMkq3HF8Pbztdg4=
	sha1:E+Mu0RfpDDiO1YF8g70Q6oBGnZ8=
Xref: reader01.eternal-september.org comp.lang.ada:57023
Date: 2019-08-09T15:03:16-07:00
List-Id: <comp.lang.ada>

Lucretia <laguest9000@googlemail.com> writes:
> You could always have a enforce named parameters compiler option,

Putting a space after the comma is generally good style and some linters
enforce or at least suggest it.  So P(1, 2) is valid but P(1. 2) should
be a syntax error.

It's interesting to hear that using named parameters at the call site is
considered good Ada style.  In Haskell and C++ one sometimes uses
separate types for the args to make sure they get passed in the right order.