Incongruent hash
jarvisb at timken.com
jarvisb at timken.com
Fri Feb 13 15:39:38 UTC 1998
However, our non-American colleagues might have fits over this one,
since in some locales the decimal "point" is written as a comma, and the
thousands/millions/billions separator is written as a period, e.g.
123,456.78 is written as 123.456,78
So building Point instances with a comma operator might cause problems
for people in such a locale. Just an observation...
Bob Jarvis
*************************** Attachment ***********************************
Date: 11 February 1998, 15:13:15 EST
>From Travis Griggs tgriggs at INTERNET
tgriggs at keyww.com
squeak at INTERNET
squeak at cs.uiuc.edu
To: squeak at INTERNET
squeak at cs.uiuc.edu
cc: recipien at INTERNET
recipient.list.not.shown:@
Reply-To squeak at INTERNET
squeak at cs.uiuc.edu
Subject: Re: Incongruent hash
Resent-Date: 11 Feb 1998 20:13:28 -0000
Mime-Version: 1.0
References: <04e9d1709130b28MAIL2 at cvtci.com.ar> from "sqrmax at cvtci.com.ar"
at Feb 11, 98 10:09:18 am <v04003a0ab1079428ccc3@[9.2.186.178]>
Content-Transfer-Encoding: 7bit
X-Mailing-List: <squeak at cs.uiuc.edu> archive/latest/750
X-Loop: squeak at cs.uiuc.edu
Resent-Sender: squeak-request at cs.uiuc.edu
David N. Smith wrote:
> One thing that has always bugged me is the notation x at y. X is not AT y.
> We'd need another notation for forming vectors and the only thing that
> comes to mind offhand is -> which is as bad, but at least it looks like a
> vector, sort of. Binary creation methods:
>
> 2 -> 3
> 2 -> 3 -> 4
I have never fully understood the use of @ either. I've always figured it had
some historical significance or was pulled out of some domain I wasn't familiar
with. I would much rather use the comma to build points from numbers. That's
what I as a highschool student was familiar with. Is this (e.g. 2,3) not the
common lay representation of a 2D point?
Travis Griggs
Key Technology
tgriggs at keyww.com
To Smalltalk! - and Beyond!
More information about the Squeak-dev
mailing list
|