[#3741] Re: Why it's quiet -- standard distribution issues — Aleksi Niemel<aleksi.niemela@...>
I think it's the feature of the mailing list archive to create a threads of
[#3756] RE: XMP on comments — Aleksi Niemel<aleksi.niemela@...>
> require "xmp"
[#3766] modulo and remainder — Dave Thomas <Dave@...>
[#3776] Kernel.rand — Aleksi Niemel<aleksi.niemela@...>
How about defining:
[#3781] Widening out discussions — Dave Thomas <Dave@...>
[#3795] Re: Array.uniq! returning nil — Aleksi Niemel<aleksi.niemela@...>
> As matz said in [ruby-talk:3785] and Dave said in [ruby-talk:1229],
Hi, Aleksi,
[#3823] Re: Array.pick — Aleksi Niemel<aleksi.niemela@...>
> > Just a general comment--a brief statement of purpose and using
[#3827] JRuby? — Aleksi Niemel<aleksi.niemela@...>
Is there or will there be Ruby equivalent of JPython?
[#3882] Re: Array.uniq! returning nil — Aleksi Niemel<aleksi.niemela@...>
> |look too strange, confusing, or cryptic. Maybe just @, $, %, &.
Hi,
[#3918] A question about variable names... — Dave Thomas <Dave@...>
[#3935] If your company uses Pallets, Skids, Boxes, Lumber, etc. — pallets2@...
[#3956] Tk PhotoImage options — andy@... (Andrew Hunt)
Hi all,
[#3971] Thread and File do not work together — "Michael Neumann" <neumann@...>
following example do not work correctly with my ruby
[#3986] Re: Principle of least effort -- another Ruby virtue. — Andrew Hunt <andy@...>
> Principle of Least Effort.
Hi,
[#4005] Re: Pluggable functions and blocks — Aleksi Niemel<aleksi.niemela@...>
Aleksi makes a question:
[#4008] Ruby installation instructions for Windows — Aleksi Niemel<aleksi.niemela@...>
I had to write these instructions for my friends. I thought it might be nice
[#4043] What are you using Ruby for? — Dave Thomas <Dave@...>
On 15 Jul 2000 22:08:50 -0500,
Hi,
[#4057] Re: What are you using Ruby for? — Aleksi Niemel<aleksi.niemela@...>
Johann:
[#4082] Re: What are you using Ruby for? — Aleksi Niemel<aleksi.niemela@...>
[#4091] 'each' and 'in' — hal9000@...
I just recently realized why the default
[#4107] Re: 'each' and 'in' -- special char problem? — schneik@...
[#4114] Method signature - a question for the group — Dave Thomas <Dave@...>
[#4139] Facilitating Ruby self-propagation with the rig-it autopolymorph application. — Conrad Schneiker <schneik@...>
Hi,
[#4158] Getting Tk to work on Windows — "Michael Neumann" <neumann@...>
Hi....
[#4178] Partly converted English Ruby/Tk widget demo working. — Conrad Schneiker <schneik@...>
Hi,
[#4234] @ variables not updated within method? — Hugh Sasse Staff Elec Eng <hgs@...>
Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
On 27 Jul 2000, Dave Thomas wrote:
[#4267] Ruby.next, Perl6, Python 3000, Tcl++, etc. -- Any opportunities for common implementation code? — "Conrad Schneiker" <schneiker@...>
Hi,
"Conrad Schneiker" wrote:
[ruby-talk:03924] Re: A question about variable names...
Hi, Dave Thomas wrote: > The rules for name construction seem to be that the first character > (which determines the name's usage) should be an upper or lowercase > letter, a dollar sign or an at sign. The remainder of the name is > drawn from [a-zA-Z0-9_]. > > So, this means that $3 and @27 and valid names for a global and > instance variable respectively. > > class Dave > def initialize > puts n > @23 = "hello" > end > def get > @23 > end > end > > However, I cannot create a symbol corresponding to the instance > variable "23" - :23 is invalid syntax. > > Then... If I create an attribute for my instance variable using > > attr "23" > > I can't use it: > > Dave.new.23 > > is parsed as passing the argument '0.23' to Dave.new. > > So... I'm wondering if allowing a digit as the first character after > the @ in an instance variable name is a good idea? > > What does the panel think? I suspect the least surprise panel is inclined to rule against it, for the above reason in conjunction with the following additional reasons. It goes against what is reasonably common (and a reasonable) practice in other languages without any strong offsetting reason. In this context (to elaborate on Hal's comment), I think most people will naturally tend to tacitly regard @ as a scope type prefix tag on a "conventional" variable name even though they know it is officially part of the variable name. $<number> variables are already (loosely speaking) special/predefined variables in a number of languages (including Ruby) that (loosely speaking) function as array element aliases. Allowing @<number> variables (which are never special) treats 9, $9, and @9 even more non-uniformly _overall_ , because it is the addition yet another exception, but an exception with a different _typical_ role/meaning than the first exception. So I just have to say nine.german_to_english to this! :-) -- Conrad Schneiker (This note is unofficial and subject to improvement without notice.)