[#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:01243] Re: Singleton classes
From: Dave Thomas <Dave@thomases.com>
Sent: Saturday, February 05, 2000 5:11 PM
> Clemens Hintze <c.hintze@gmx.net> writes:
<<snip>>
> > 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 we're agreeing! I think your original note mentioned a
> "closure object", and I was simply suggesting for consistency we
> should call objects by their class's name were possible a String
> object, a File object, and a Proc object. I agree absolutely we need
> to distinguish between unbound blocks and closures.
I'm all for consistency attained by "calling by (user view of) function"
rather than "calling by implementation". (English pun; sometimes "calling"
means "naming". :-) I think this would help beginners learn Ruby, while
complying with the principle of least surprise for more advanced users.
But out of curiosity, what terms (if any) are used for these sorts of things
(and the other things mentioned earlier in this thread) by other OO
languages (for example, CLOS/Lisp, Eiffel, Smalltalk, Python, and (proposed
extensions to) Java) in particular, and by the computer science community in
general? Do they have any terms worth copying?
It might be useful to have a FAQ entry for a comparison of Ruby OO
things/terms and those of other OO languages. (Cases were the same terms are
used should probably also be included, if there are subtle or significant
differences in behavior/implementation.) This might be a useful addition to
the www.ruby-lang.org language comparison page.