[#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@...>
[#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,
[#1981] Time::at — "David Douthitt" <DDouthitt@...>
or whatever the right syntax is :-)
[#1989] English Ruby/Gtk Tutorial? — schneik@...
Hi,
SugHimsi(%HeIsSaidJustToLoseHisPatienceOnThisSubject;-).
[#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@...>
[ruby-talk:02318] Re: Question about attribute writers
Dave Thomas writes: > Clemens Hintze <c.hintze@gmx.net> writes: > > > At least I would expect it! It is like answered in your FAQ! How does > > Ruby determine what a variable is? It is really stright-forward, IMHO. > > > > Look if there was an assignment before > > yes => compile a variable access > > no => compile a method call. > > True - I asked the wrong question. Rather than asking "is this the > expected behavior", I guess I meant "is this the behavior that someone > would expect?" It seems to violate the principle of least surprise. Hmm difficult thingy here, I think. I would never assume that age = 12; could invoke a method, because I *know* that this syntax normally means assignment to a local variable. It would be very strange to me to use a method 'age=', if I can access @age directly. Invoking a method would furthermore be more costly. I admit this it-could-be-a-variable-or-a-method-call thingy is one of the things, that disturbes me also sometimes in Ruby. > > Perhaps a warning would a good idea in these circumstances: > > warning: local variable eclipses instance method Erhm ... IMHO this warning is wrong! Because there is *no*syntax* that allow 'age = 12' meaning a method call to 'age='. So if this is invalid syntax concerning the Ruby grammar, how could we issue a warning that this method call would be globbered? We *are*not* able to call the method like this. And if we use self.age = 12 as intended, all ambiguities are removed! I would propose the opposite, if we really want to issue an warning. The warning should be issued for the case age / 12 where I want to divide the value of a variable 'age'. But because this variable does not exists, I will get a method call compiled. Here the compiler could issue an warning like: warning: ambigues variable access or method call I could by-pass this warning then by explicitely writing: age() / 12 But I admit, that this solution would probably issue too much warnings because the 'age / 12' syntax is often used! Perhaps it would be better to not change anything, and describe this case very carefully in the books and docs. Every language has its gotchas. We cannot eliminate all of them. This is one of Ruby. > > Dave \cle -- Clemens Hintze mailto: c.hintze@gmx.net