[#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:01347] Say Hi
mengx@nielsenmedia.com writes: > Hi: Hi too, may I take this opportunity to welcome you here? It is fine to see, how fast the Ruby community seems to grow :-) > I Studied Ruby's document and coding for about two days and decided > to start using Ruby even though I have used Python for 5 years, > among other languages. In my opinion, Ruby is what Python 3000 > should be if all these $$$$ can be removed :-) (for some reason, I > never like $$$$ so I chose Python (also due to neat syntax) over > Perl). Ruby is ultimate dynamic language. You have nearly the same background like me! I am also coming from Perl->Python->Ruby! And I have to recognize ever and ever again *how* dynamically Ruby is, indeed. After a year of usage, there are still some facts that surprise me yet! :-) > Just a quick thought after going through Array class, would it be > possible to revise the pop and push method to accept index argument > such that pop(0) act like shift and pop(-1) like current pop push > (obj, 0) like unshift and push(obj, -1) like current push. shift > and unshift are too Perlitical :-). I know I can subclass it, but > having it builtin would be better. > I beg pardon, but I would not like it! I think it is not too good to have too multifunctional methods. Every method should has its behavior. push and pop are used to handle an Array like a stack not for indexing it. shift and unshift do the same but from the opposite end. They are not necessarily coming from Perl. Nearly all UNIX shells treat them like Perl. I assume Perl has taken that behavior from the UNIX shells. IMHO, it would be better to allow Array::delete_at to receive also negative arguments like Array::[]. If it would do, it would really be what you want to have. Then you could use: arr = [9,8,7,6] first = arr.delete_at(0) # first element assigned and deleted last = arr.delete_at(-1) # last element now. p arr # would print [8,7] What do you think about it? > Thanks > > -Ted Meng \cle -- Clemens Hintze mailto: c.hintze@gmx.net