[#1215] Tk widget demo; English Tk docs?; Java 1.2 Swing — "Conrad Schneiker" <schneiker@...>
Hi,
[#1218] Trivial FAQ bug — Dave Thomas <Dave@...>
[#1229] A vote for old behavior — Dave Thomas <Dave@...>
[#1232] Any FAQ requests, updates, ... — Dave Thomas <Dave@...>
[#1233] Singleton classes — Dave Thomas <Dave@...>
[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>
[#1307] Ruby/GTK 0.23 released — Hiroshi IGARASHI <igarashi@...>
Hi all,
From: Hiroshi IGARASHI <igarashi@ueda.info.waseda.ac.jp>
From: "Conrad Schneiker" <schneiker@jump.net>
On Fri, Feb 18, 2000 at 09:37:27PM -0500, Yasushi Shoji wrote:
[#1322] FAQ: Ruby acronyms — "Conrad Schneiker" <schneiker@...>
In the spirit of TABWTDI (there are better ways to do it), I'd like to
[#1341] Vim syntax file — Mirko Nasato <mirko.nasato@...>
Hi,
On Mon, Feb 14, 2000 at 05:44:39PM +0100, Mirko Nasato wrote:
[#1354] Say hi (bis) — Pixel <pixel_@...>
hi all,
[#1355] nice sample for functional stuff — Pixel <pixel_@...>
what about having map in standard (and map_index too)?
[#1373] Ruby Language Reference Manual--Glossary — "Conrad Schneiker" <schneiker@...>
I was going to print the Ruby Language Reference Manual when I noticed that
[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>
Conrad writes:
[#1379] Re: Yield — Andrew Hunt <andy@...>
>From: "Conrad Schneiker" <schneiker@jump.net>
[#1384] Re: Say Hi — mengx@...
My suggestion was to try to find a more comfortable method name (to me, and
[#1392] Re: Some Questions - Parameterised Types / Invariants — Andrew Hunt <andy@...>
>1. Parameterised Types / Template Classes
[#1398] Bignum aset — Andrew Hunt <Andy@...>
[#1488] Discussion happens on news.groups — Clemens Hintze <c.hintze@...>
Hi,
[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>
Hello Ian,
On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:
[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>
((FYI: This was sent to the Ruby mail list.))
From: "Conrad Schneiker" <schneiker@jump.net>
[#1528] ruby <=> python — Quinn Dunkan <quinn@...>
Hello! I'm new to ruby-talk, and mostly new to ruby. I'm making a document
[#1551] Ruby thread scheduling buglet — Ian Main <imain@...>
[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>
The following message is a courtesy copy of an article
[#1591] Certain char's not recognized by "." in regex? — Wes Nakamura <wknaka@...>
[#1592] Race condition in Singleton — Dave Thomas <Dave@...>
[ruby-talk:01241] Re: Singleton classes
Dave Thomas writes:
> Clemens Hintze <c.hintze@gmx.net> writes:
>
> > Both, the old terminology and your proposed one, it too much in the
> > hidden internal direction, IMHO. I would call it for what it does, not
> > how it work internally.
>
> I think that's a good point. Phrasing from the user's perspective,
> rather than implementation, would be good.
>
> I quite like the idea of thinking about it as an object extension, but
> even that has problems. What are we extending it with?
>
> def foo.bar end
>
> is also a kind of object extension.
>
> It's like we're subclassing the class of an object. How about
> 'anonymous subclass'?
>
Hmmm... Why introducing the concept of a new class herein? From the
users point of view, what is the difference between
obj = Myclass.new
class << obj
def what
print "Myclass\n";
end
end
and
obj = Myclass.new
def obj.what
print "Myclass\n";
end
? I would say nothing, on the first glance! Both seems to be object
extensions. So both could be named equivalent, or not? Why should we
mention that it is done via anonym subclasses? Therefore I would call
it something like object extension. A class extension would be:
class Myclass
def who
print "here\n";
end
end
if Myclass already exists.
>
> > In the past there was a problem with the terms of iterators. matz has
> > begun to clarify it, but perhaps there are some places where it is
> > still inconsistent yet? It should be called either block (in source)
> > or closure (as object) now.
>
> Wouldn't the object be a Proc object?
Yes. Every closure is an instance of class Proc. A block, however, is
only code surrounded by '{' and '}' or 'do' and 'end'. We can use
'lambda' or 'proc' or 'Proc.new' to convert a block to a closure
(means Proc instance). Or we could use 'yield' to execute a block.
I think this difference should be clear and consistent throughout all
documentation, because it is a very important and flexible feature of
Ruby.
>
>
> Dave
>
\cle
--
Clemens Hintze mailto: c.hintze@gmx.net