Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!tcdcs!csvax1.cs.tcd.ie!ecarroll
From: ecarroll@csvax1.cs.tcd.ie (Eddy Carroll)
Newsgroups: comp.sys.amiga.tech
Subject: Argument lists (was Re: Symbolic Links and the AREXX: device)
Message-ID: <53604@csvax1.cs.tcd.ie>
Date: 11 Sep 89 18:39:03 GMT
References: <14083@netnews.upenn.edu> <45274@bbn.COM> <13557@well.UUCP>
Organization: Computer Science Department, Trinity College Dublin
Lines: 17

In article <13557@well.UUCP>, shf@well.UUCP (Stuart H. Ferguson) writes:
> Why can't the computer
> clerisy come up with idiot-proof arguments lists!?  My favorite is "strcpy;"
> I can *never* remember the order for the arguments.  And getting them wrong
> will fry your code as bad as shorting any op-amp.

For what it's worth, I remember strcpy, memcpy etc. by mentally sticking an
'=' between the two arguments. I forget where I read this, but it's never
confused me since. :-)

As I recall, ADA lets you specify procedure/function parameters in any order
you like, as long as you remember to qualify them with the formal name of
the parameter. So do most of the CLI commands, for that matter.
-- 
Eddy Carroll               ----* Genuine MUD Wizard  | "You haven't lived until
INTER: ecarroll@vax1.tcd.ie                          |   you've died in MUD!"
 UUCP: {..uunet}!mcvax!ukc!vax1.tcd.ie!ecarroll      | -- Richard Bartle