[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>
From: Jon Babcock <jon@kanji.com>
Thanks.
From: Jon Babcock <jon@kanji.com>
Ah, thanks, I think I get it, a slightly different nuance then.
From: Jon Babcock <jon@kanji.com>
'Because all of Ruby has been...' -> 'Because Ruby has been...'?
[#5221] better way to say 'recursive join' — Yasushi Shoji <yashi@...>
in [ruby-dev:6289], Shugo Maeda suggested better name for recursive
[#5240] Ruby for Win32/DOS — Dennis Newbold <dennisn@...>
Not all of us are blessed with the opportunity to be able to develop on
[#5254] problem: undefined method `size' for File — "葡ic Santonacci" <Eric.Santonacci@...>
Hi all,
HI,
[#5264] Re: problem: undefined method `size' for Fil e — Aleksi Niemel<aleksi.niemela@...>
matz critizes good solution argumenting with features lacking from some
[#5268] Proper ConditionVariable usage? — Aleksi Niemel<aleksi.niemela@...>
Abstract
On Wed, 04 Oct 2000 07:05:22 +0900, Aleksi Niemelwrote:
In message <20001004110040.A26666@xs4all.nl>
Hi,
[#5276] Re: Ruby Book Eng tl, ch1 question — schneik@...
[#5310] Errata for Ruby Book? — Jon Babcock <jon@...>
[#5318] Redefining super method as singleton? — Robert Feldt <feldt@...>
On Fri, 6 Oct 2000, Yukihiro Matsumoto wrote:
[#5329] Ruby vs PHP ? — "Valerio Bamberga" <bamberga@...>
Hi!
[#5331] Unit testing network code? — Hugh Sasse Staff Elec Eng <hgs@...>
Can someone give me pointers on how to Unit Test code that is run on
> I think maybe one would test each end on its own first, faking the
[#5335] string streams in Ruby? — Hugh Sasse Staff Elec Eng <hgs@...>
Is there any way, without going through "modifying the internals",
[#5346] Is Ruby "enough better"? — Gabriel Lima <Gabriel.Lima@...>
Hi.
[#5364] Allowing *ary's in the middle of a camma separated list — "Akinori MUSHA" <knu@...>
Hi,
Hi,
At Tue, 10 Oct 2000 14:17:24 +0900,
[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>
OK, here is what I think I know.
At Wed, 11 Oct 2000 11:37:25 +0900,
Hi,
Hi,
Hi,
Hi,
[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>
At Thu, 12 Oct 2000 03:49:46 +0900,
Thanks for the input.
At Thu, 12 Oct 2000 04:53:41 +0900,
At Thu, 12 Oct 2000 07:25:03 +0900,
oops, I didn't read this one before I went out for food..
At Thu, 12 Oct 2000 09:59:19 +0900,
[#5437] Editor recommandations? — "Chris Morris" <chrismo@...>
Any recommendations on editors for Ruby script on Windows?
[#5471] 2 ideas from Haskell — Mark Slagell <ms@...>
Do either of these interest anyone:
[#5479] Some newbye question — Davide Marchignoli <marchign@...>
I am reading the documentation I found about ruby but several points
[#5480] InstallShield version for Ruby soon... — andy@... (Andrew Hunt)
Okay folks,
[#5489] Regexp#matches — Aleksi Niemel<aleksi.niemela@...>
Would someone object aliasing matches for match in Regexp?
[#5505] Sorry, What is Ruby Book — Mansuriatus Shahrir Amir <chioque@...>
Sorry if this information is somewhere obvious. I just stumbled upon
[#5516] Re: Some newbye question — ts <decoux@...>
>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:
Hi,
On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:
matz@zetabits.com (Yukihiro Matsumoto) writes:
Dave Thomas <Dave@thomases.com> wrote:
Hi,
> Proposal a and b have incompatibility. I'm not sure it's worth it.
>>>>> "Y" == Yukihiro Matsumoto <matz@zetabits.com> writes:
On Mon, 16 Oct 2000, ts wrote:
>>>>> "Y" == Yukihiro Matsumoto <matz@zetabits.com> writes:
[#5558] GC: malloc_memories — Mathieu Bouchard <matju@...>
Hi,
> |precipitate a new GC cycle if lots of resizing is done. My biggest
[#5570] Notes about GC — Mathieu Bouchard <matju@...>
[#5600] passing single or multiple strings. — Hugh Sasse Staff Elec Eng <hgs@...>
With multple assignments I can get nested arrays "shelled" (like peas)
In message "[ruby-talk:5600] passing single or multiple strings."
[#5603] debug command list in English — "Morris, Chris" <ChrisM@...>
I found this page which lists the interactive debugger commands ... anyone
[#5619] lint? — "Swit" <swit@...>
Is there something like lint for Ruby? I'd like to find NameErrors before
[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>
There has been discussion on this list/group from time to time about
Hugh Sasse Staff Elec Eng wrote:
On Sat, 21 Oct 2000, Charles Hixson wrote:
[#5715] Help: sockets broken — jason petrone <jp@...>
I just compiled ruby 1.6.1 on an openbsd 2.6 machine(x86).
[#5716] Re: Array#insert — Aleksi Niemel<aleksi.niemela@...>
> From: jweirich@one.net [mailto:jweirich@one.net]
[#5727] String#slice surprise — "Guy N. Hurst" <gnhurst@...>
Hi,
Dave Thomas wrote:
[#5787] Shells and Ruby — "Dat Nguyen" <thucdat@...>
Hello all,
[#5850] Re: Array#insert rehashed — Aleksi Niemel<aleksi.niemela@...>
Dave asks for:
[#5862] succ but no pred? (& the MURKY award) — "Hal E. Fulton" <hal9000@...>
First of all, a serious question:
[#5873] Integer(String) weirdness for a ruby newbie — Stoned Elipot <Stoned.Elipot@...>
Hi,
[#5881] Q:what about "Programming Ruby"? — Gabriel Lima <Gabriel.Lima@...>
Hi to you all.
[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>
Hello fellow rubyists,
On Fri, 27 Oct 2000, hipster wrote:
[#5947] Hash.new {block} / Hash#default_proc{,_set} — "Brian F. Feldman" <green@...>
I've done very little testing, but I think I've successfully implemented the
[ruby-talk:5623] Re: Flame-bait and this is private post
Mr. Matsumoto, > |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. You are going to try to teach your daughter a pure abstraction? I feel very sorry for her or anyone else that makes such an attempt. That involves memorization rather than internalization. You have much more knowledge of English than you may think. If she has none and attempts to learn Ruby in it's current format, you are creating an almost insuperable task for her. My wife is a reading teacher in two romanized languages, Spanish and English. Normally, we say that I child learns to read once, but may then learn to read other languages. Because of the different brain usage in a partially symbolic language such as Japanese or Chinese, it seems logical that reading between such languages and romanized languages is such a different process as to constitute learning to read twice. If she has no English when she learns Ruby, she will learn to "read" Ruby, and then try to learn English. I find it difficult to imagine how badly that will turn her sense of logic. "This is an array sort", is a perfectly logical and normal English sentence. "array.sort" does not depart far from that. > (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. What you want and what you can accomplish when dealing with perception in human beings are two entirely different things. Again, nothing is lost if you follow "natural" English and much is gained in the intuitive use of the Ruby language. When you chose English as the basic word source for Ruby, you implicityly hauled all that baggage with it. Now, you want to throw it all away and cannot no matter what you state. Unless someone speaks no English and has no experience of it's structure and usage, one cannot help but seek some meaning through English rather than Ruby. This is natural and to be expected. It actually cannot be prevented. In my neighborhood, we call what you are attempting "rowing upstream". > 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. Actually, you are right and you are wrong. You are obviously free to proceed in any manner that you choose. A certain number of people will go with you almost anywhere. Taste is one thing, human nature is another. Taste can be adjusted with some time and difficulty, human nature, really, not at all. When you resist it, you are on a fool's errand and in the long run, you will fail. I will rephrase your last sentence. Some hate them, some love them, most are so inarticulate and unexamined as to not be able to express what they intuitively act on. Our children are our unwitting victims. Think carefully how you lead your's. Everett L.(Rett) Williams rett@gvtc.com