[#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:5579] Re: Flame-bait and this is private post

From: matz@... (Yukihiro Matsumoto)
Date: 2000-10-16 08:48:02 UTC
List: ruby-talk #5579
Hi,

I feel it's appropriate to talk about this topic in the list, unless
it goes to a flame war.  So I put back the personal message to the list.

In message "Re: Flame-bait and this is private post"
    on 00/10/16, "Everett L.(Rett) Williams" <rett@gvtc.com> writes:

|Language chauvinism is no more attractive than any other form of
|chauvinism.

Well, if you felt language chauvinism in my words, that was not what I
meant.  In fact, I am opposite to language chauvinism to any specific
natural language (including Japanese and English).  You felt like that
probably due to my lack of English skills.

I agree that the method invocation syntax in Ruby

  receiver.method(arguments)

resembles

  Subject Verb Objectives

in English, and receiver often corresponds to the single real world
entity.  So I feel sympathy to the people who want method names in the
form of third person singular, e.g. exists, has_key, etc.

But I decided not to do so, because of the following 2 reasons.

 (1) As you said, I borrowed a lot of WORDS from English.  But I don't
     want to make Ruby programmers to know English SYNTAX.  My oldest
     child will learn Ruby programming in several years (she is 8
     now).  But it'll take years for her to learn English grammar.
     She can memorize some alphabetical sequences.  In this case, I
     want her to learn programming, not English.

     In fact, array.sort should be a wrong method name if English
     correctness is pursued, for example.

 (2) You didn't claim all method names which are verbs should be in
     the form of third person.  Some verbs in the third person make
     you feel natural; others not.  Knowledge of English grammar is
     required to distinguish this, I think.  Again I want to be apart
     from English grammar.

Despite all the excuses I listed above, in conclusion, it's all up to
the taste of programmer.  Some hate them, some love them, most don't
care.

							matz.

In This Thread