[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5599] Re: Regexp#matches

From: hal9000@...
Date: 2000-10-16 17:40:02 UTC
List: ruby-talk #5599
In article <39EA7359.4E4EE62F@gvtc.com>,
  "Everett L.(Rett) Williams" <rett@gvtc.com> wrote:
> matz,

[snip]

> Since English is not your
> native language, you might not know that "third person, singular"
> has nothing to do with the usage of "exists" rather than "exist".
> Rather,
> it stems from the necessity in English of having the noun and the verb
> agree whether we are using plural or singular. If your method normally
> refers to multiple items, then "they exist". If it normally refers to
a
> single item, then "it exists". If it goes both ways, then either would
> be logical. Since we normally, philosophically refer to existence as
> a singular thing, even when referring to a group, "exists" might be
> more appropriate.
>

Well, flame bait or not, I'll venture a comment. This response is
intended neither as flame nor troll.  :)

An object, however many components it may have, is a singular entity.
We can't call a method with more than one receiver. So Matz is ignoring
the plural. And his assessment that the third person is the proper
person is correct; it makes no sense to think of an object in the
first or second person. So, in English, "I exist," "you exist," but
"he/she/it exists" (third person).

So offhand, though Matz's English is flawed, I'd say his theoretical
knowledge of English grammar is comparable to yours or better.

Now this reasoning seems to prefer "exists" to "exist." But I will
continue.

The infinitive form of the verb (which English typically
uses with first and second person singluar subjects) is the "real" or
basic form of the verb. This is true in English, Latin, French, German,
Italian, and Spanish, to name a few. So using the infinitive form is
actually conducive to non-native speakers of English learning Ruby
more easily.

What is more, the English.rb provides an out for people who simply can't
tolerate little discrepancies like that.

But the bottom line is this: indiivduals may disagree with trivial
decisions like this one, but they have their own logic and are
defensible. They are not arbitrary or haphazard. Though the words
in Ruby come from English, Ruby isn't English.

I do prefer "matches" to "match." But if conflicts with a prior design
decision, it's not worth bothering with, especially since I can define
"matches" myself anytime I want.

Enough said. Let's talk about programming again.

--
Hal Fulton


Sent via Deja.com http://www.deja.com/
Before you buy.

In This Thread