[#1649] Re: New Ruby projects — Yukihiro Matsumoto <matz@...>
The following message is a courtesy copy of an article
[#1672] Re: Ruby 1.4 stable manual bug? — Yukihiro Matsumoto <matz@...>
The following message is a courtesy copy of an article
[#1673] Re: Possible problem with ext/socket in 1.5.2 — itojun@...
[#1694] Conventions for our Ruby book — Dave Thomas <Dave@...>
[#1715] Install postgresql support — Ikhlasul Amal <amal@...>
Hi all,
Hi,
[#1786] Is this a bug? — Clemens Hintze <clemens.hintze@...>
(mailed & posted)
[#1814] Objects nested sometimes. — Hugh Sasse Staff Elec Eng <hgs@...>
I am attemptiong to write a package which consists of a workspace
[#1816] Ruby 1.5.3 under Tru64 (Alpha)? — Clemens Hintze <clemens.hintze@...>
Hi all,
Hi,
Yukihiro Matsumoto writes:
Hi,
Hi,
[#1834] enum examples? — Hugh Sasse Staff Elec Eng <hgs@...>
Has anyone any examplse of using the Enumerable module? I've had a
[#1844] Minor irritation, can't figure out how to patch it though! — Hugh Sasse Staff Elec Eng <hgs@...>
I was considering how difficult it would be to patch Ruby to accept
[#1889] [ruby-1.5.3] require / SAFE — ts <decoux@...>
[#1896] Ruby Syntax similar to other languages? — "David Douthitt" <DDouthitt@...>
From: Yukihiro Matsumoto <matz@netlab.co.jp>
[#1900] Enumerations and all that. — Hugh Sasse Staff Elec Eng <hgs@...>
Thank you to the people who responded to my questions about Enumerated
Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
On 16 Mar 2000, Dave Thomas wrote:
[#1929] Re: Class Variables — "David Douthitt" <DDouthitt@...>
| "David Douthitt" <DDouthitt@cuna.com> writes:
[#1942] no Fixnum#new ? — Quinn Dunkan <quinn@...>
Ok, I can add methods to a built-in class well enough (yes I know about succ,
[#1989] English Ruby/Gtk Tutorial? — schneik@...
Hi,
[#2022] rb_global_entry — ts <decoux@...>
[#2036] Anonymous and Singleton Classes — B_DAVISON <Bob.Davison@...>
I am a Ruby newbie and having some problems getting my mind around certain
[#2069] Ruby/GTK+ question about imlib --> gdk-pixbug — schneik@...
[#2073] Re: eval.rb fails — "Dat Nguyen" <thucdat@...>
The doc is fine, this happens only if you try to execute 'until' block
On Wed, 22 Mar 2000, Dat Nguyen wrote:
[#2084] Scope violated by import via 'require'? — Clemens Hintze <c.hintze@...>
Hi,
[#2104] ARGF or $< — Hugh Sasse Staff Elec Eng <hgs@...>
Has anyone any examples of how to use ARGF or $< as I cannot find much
Hi.
[#2165] Ruby strict mode and stand-alone executables. — "Conrad Schneiker" <schneiker@...>
Some people want Ruby to have a strict compile mode.
[#2203] Re: parse bug in 1.5 — schneik@...
[#2212] Re: Ruby/Glade usage questions. — ts <decoux@...>
>>>>> "m" == mrilu <mrilu@ale.cx> writes:
[#2241] setter() for local variables — ts <decoux@...>
[#2256] Multiple assignment of pattern match results. — schneik@...
[#2267] Re: Ruby and Eiffel — h.fulton@...
[#2309] Question about attribute writers — Dave Thomas <Dave@...>
Clemens Hintze <c.hintze@gmx.net> writes:
[ruby-talk:01696] Re: Conventions for our Ruby book
Hi, From: Dave Thomas <Dave@thomases.com> Subject: [ruby-talk:01694] Conventions for our Ruby book Date: 02 Mar 2000 11:38:37 -0600 > The other thing we like about this approach is that the method > signatures are valid Ruby syntax. I think it's a good approach. However, "String.downcase" (to refer String#downcase) is syntactically valid, but semantically not. So, I think, "String.downcase" is not so good. > Existing Ruby documentation gets around this by using the '#' > notation. It would say "see String#downcase" to refer to an instance > method in String. > > Although its a good differentiator, it worries us slightly, because it > isn't Ruby syntax. We though it might be confusing. > > So, we were wondering what people thought. Is the '#' notation a good > one? Will is confuse newcomers who pick up the book? Is there any > alternative that might be easier to read (For example, String.new, but > <i>String</i>.downcase)? What should we do? In reference section, I don't worry about newcomer's confusion. Newcomers are too new to be confused in the reference section!! So, I think, '#' is not so bad for newcomers, unless there are hundreds of '#'s per page. (I think, newcomers would be attracted in introductory sections, TOC, index, and brief look of the reference) IMHO, the point is beginners, who begin to use the reference section. The important is how to make understand beginners, who read the book, as fast as you can. It have to be explained in early sections, in introductory part of the reference section, and in index too. From another point of view, '#' is already used in several ruby documents, including matz's book and mailing lists. IMO, making newcommers and beginners familier with the '#' notation is good strategy, for Ruby (I mean not only for the book). To follow the strategy, I recommend '#' rather than <i>String</i>.downcase. And about your book, '#' might be in other font than that of Ruby codes. FYI, In matz's book, Class#instance_method notation is used, and it's explained in footnote (p.55 in section 2). I think, this means, '#' is thought to be ordinal, at least by matz. And AFAIK, in ruby-list there is no complaint about '#' of matz's book. (Is this wrong? please correct) Regards, Hiwada -- Kazuhiro HIWADA <hiwada@kuee.kyoto-u.ac.jp> excuse my buggy english