Xref: utzoo comp.lang.c:7989 comp.lang.misc:1191
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!umd5!vrdxhq!bms-at!stuart
From: stuart@bms-at.UUCP (Stuart D. Gathman)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: Re: The D Programming Language
Message-ID: <587@bms-at.UUCP>
Date: 10 Mar 88 21:26:58 GMT
References: <25284@cca.CCA.COM> <700@l.cc.purdue.edu>
Organization: Business Management Systems, Inc., Fairfax, VA
Lines: 28
Summary: Amen

In article <700@l.cc.purdue.edu>, cik@l.cc.purdue.edu (Herman Rubin) writes:
> but even for direct operators.  For example, the infamous frexp function
> in C should not have the syntax

> 	y = frexp(x,&n);

> but

> 	y,n = frexp(x);

> This would, for example, allow n to be in a register, which is probably 
> where it should be anyhow.

> Another example would be to have

> 	q,r = a///b;

> where the quotient and remainder are simultaneously produced.  Possibly

Another example is string comparison.  I use a string compare function
that returns the index of the first different character.  I also
need the gt/lt/eq result.  Fortunately, in this case it is easily 
computed by recomparing the chars at the index.  This is another case
of a double valued hardware primitive.  (Available on all three
of the architectures we use: Series/1, 80286, 68020.)
-- 
Stuart D. Gathman	<stuart@bms-at.uucp>
			<..!{vrdxhq|daitc}!bms-at!stuart>