[#5999] Re: Custom installation (1.6.1) — ts <decoux@...>
>>>>> "D" == David Suarez de Lis <excalibor@demasiado.com> writes:
[#6019] Time.local bug? — hal9000@...
Please tell me this is a bug, not a feature.
[#6028] Ref.: Re: Time.local bug? — David Suarez de Lis <excalibor@...>
Hi,
[#6042] Re: Time.local bug? — ts <decoux@...>
>>>>> "H" == Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
[#6074] Re: Cygwin conflicts — "Conrad Schneiker/Austin/Contr/IBM" <schneik@...>
Conrad Schneiker wrote:
[#6078] Programming Ruby ranking — Aleksi Niemel<aleksi.niemela@...>
Just a small note how the Ruby book sells:
[#6083] ANN: Single step Ruby installation for Windows — Dave Thomas <Dave@...>
[#6092] Re: detect:ifNone: in Ruby — Aleksi Niemel<aleksi.niemela@...>
> I like it. You can also mess around with the built in classes to get
[#6097] Re: detect:ifNone: in Ruby — Aleksi Niemel<aleksi.niemela@...>
matz queries:
[#6102] What would a Ruby browser look like? — Dave Thomas <Dave@...>
[#6106] Re: What would a Ruby browser look like? — "Conrad Schneiker/Austin/Contr/IBM" <schneik@...>
Stephen White writes:
People are already talking about using Tk to do this, or doing it as a WWW
[#6121] More Date/Time inconsistencies — David Suarez de Lis <excalibor@...>
Hi all,
[#6122] Ruby Book, Eng. tl, 6.1 -- aimai ? — Jon Babcock <jon@...>
[#6138] Thoughts on a Ruby browser — hal9000@...
I have to issue a disclaimer first, that I am not a code browser user,
[#6143] Re: What would a Ruby browser look like? — "Conrad Schneiker/Austin/Contr/IBM" <schneik@...>
Matz writes:
[#6149] Ruby hi(gh), and pointer to Jotto program — David Alan Black <dblack@...>
Hello --
David Alan Black <dblack@candle.superlink.net> writes:
[#6181] Minimal but practically useful Ruby browser? — "Conrad Schneiker/Austin/Contr/IBM" <schneik@...>
Hi,
[#6206] Re: marshal.dump again — ts <decoux@...>
>>>>> "H" == Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
[#6220] ruby-lang.org — Dave Thomas <Dave@...>
[#6246] Re: quiz of the week — "Brian F. Feldman" <green@...>
"Brian F. Feldman" <green@FreeBSD.org> wrote:
> In case anyone wants something else to try an example of how fun
[#6288] lchown()/etc. and Unix syscall completeness — "Brian F. Feldman" <green@...>
Ruby as it is now isn't very consistent with the system calls it provides.
[#6316] Q: Sandbox security, SAFE and system — Robert Feldt <feldt@...>
Hi,
[#6346] Re: Another Smalltalk control structure idea — "Conrad Schneiker/Austin/Contr/IBM" <schneik@...>
Matz writes:
On Tue, 14 Nov 2000 15:29:31 +0900, Conrad Schneiker/Austin/Contr/IBM wrote:
[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>
>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:
Hello again --
matz@zetabits.com (Yukihiro Matsumoto) writes:
[#6383] 1.6.x documentation. — Hugh Sasse Staff Elec Eng <hgs@...>
On Tue, 14 Nov 2000, Yukihiro Matsumoto wrote:
[#6386] lots of Threads — Hugh Sasse Staff Elec Eng <hgs@...>
If I have an array to be filled with computationally heavy stuff,
Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
On Thu, 16 Nov 2000, Dave Thomas wrote:
On Thu, 16 Nov 2000 19:59:07 +0900, Hugh Sasse Staff Elec Eng wrote:
[#6412] clas << a & Pascal's with <record> do...end — Hugh Sasse Staff Elec Eng <hgs@...>
I was thinking that when a lot of work must be done on an object
[#6417] Where is T_RANGE? — Robert Feldt <feldt@...>
Hi,
[#6444] Ruby tokenizer for Ruby — Charles Hixson <charleshixson@...>
Does anyone know of a Ruby tokenizer for Ruby? In particular, I am bother
[#6461] Is there a FITS_IN_UINT(v)? — Robert Feldt <feldt@...>
Hi,
Robert Feldt <feldt@ce.chalmers.se> writes:
[#6476] %x{...} and ` not working? — Niklas Backlund <d99-nba@...>
Hi,
[#6485] Re: GUI in ruby — "Conrad Schneiker" <schneik@...>
Hi,
[#6491] comp.lang.tcl -- The "Batteries Included" Distribution [LONG] — "Conrad Schneiker" <schneik@...>
Hi,
On Tue, 21 Nov 2000 16:58:30 +0900, Conrad Schneiker wrote:
[#6503] redefining methods in a hierarchy. — Hugh Sasse Staff Elec Eng <hgs@...>
If I have an object which I know to be a subclass of a subclass (at lease)
[#6518] Re: Question about the behavior of write att ributes in blocks — Aleksi Niemel<aleksi.niemela@...>
> Is it at all possible to write an iterator, which allows assignments
Thank you for explanation - the output of "x".inspect() is
"Christoph Rippel" <chr@subdimension.com> writes:
I lifted the following two lines from your (great) book - Page 285
[#6521] Time Trouble — Niklas Backlund <d99-nba@...>
Hi,
[#6523] alias_method and > and < — Hugh Sasse Staff Elec Eng <hgs@...>
The operators > and < don't seem to be in the list of things one cannot
[#6550] Note on docs for Array#reverse! — Robert Feldt <feldt@...>
[#6571] Re: Ruby/C extension build question — Arjen Laarhoven <arjen@...>
Oops:
[#6579] ANN: Ruby/GDChart 0.0.1 available — Arjen Laarhoven <arjen@...>
Hi all,
[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>
Hello --
David Alan Black <dblack@candle.superlink.net> wrote:
David Alan Black <dblack@candle.superlink.net> writes:
David Alan Black <dblack@candle.superlink.net> writes:
On Tue, 28 Nov 2000, Dave Thomas wrote:
[#6597] Question on sort! — Dave Thomas <Dave@...>
matz@zetabits.com (Yukihiro Matsumoto) writes:
Hi,
> The latter can be avoided if one follows the no-bang-method-chain
[#6642] Hash with a key of nil ? — rpmohn@... (Ross Mohn)
While reading data in from a file and populating a hash, I accidentally
[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>
Ross asked something about widely known and largely ignored language (on
aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in
> >Use a hash. Here's code to do both and more. It assumes that
----- Original Message -----
Hi,
[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)
I'm coming to Ruby with a Python & Common Lisp background.
matz@zetabits.com (Yukihiro Matsumoto) writes:
[#6666] Suggestion for addition to Begin/End syntax — drew@... (Andrew D. McDowell)
Hi all.
[ruby-talk:6630] RUBY NEWSGROUP FAQ -- Welcome to comp.lang.ruby! (Revised 2000-11-11)
RUBY NEWSGROUP FAQ -- Welcome to comp.lang.ruby! (Revised 2000-11-11)
This FAQ contains information for those who want to:
1) learn more about Ruby, and want to
2) post to comp.lang.ruby.
This FAQ is normally posted every 2 weeks or so.
1 About Ruby.
1.1 What is Ruby?
Ruby is a very high level, fully OO programming language. Indeed,
Ruby is one of the relatively few pure OO languages. Yet despite
its conceptual simplicity, Ruby is still a powerful and practical
"industrial strength" development language.
Ruby selectively integrates many good ideas taken from Perl,
Python, Smalltalk, Eiffel, ADA, Clu, and Lisp. (Ruby is more
fully OO than Python in so far as basic types such as hashes can
be subclassed. See Ruby FAQ 1.4.) Ruby combines these ideas in a
natural, well-coordinated system that embodies the principles of
least effort and least surprise to a substantially greater extent
than most comparable languages--i.e. you get more bang for your
buck, and what you write is more likely to give you what you
expected to get. Ruby is thus a relatively easy to learn, easy to
read, and easy to maintain language, yet it is very powerful and
sophisticated.
In addition to common OO features, Ruby also has threads,
singleton methods, mix-ins, fully integrated closures and
iterators, plus proper meta-classes. Ruby has a true
mark-and-sweep garbage collector, which makes code more reliable
and simplifies writing extensions. In summary, Ruby provides a
very powerful and very easy to deploy "standing on the shoulders
of giants" OO scaffolding/framework so that you can more quickly
and easily build what you want to build, to do what you want to
do.
For many former Perl and Python users seeking a more uniform and a
more powerful set of higher level OO programming capabilities
without the complexities of C++, or the compromises of Java, or
the subtleties of Smalltalk, Ruby is a "much better Perl than
Perl" and a "significantly better Python than Python". (This is no
small feat, since these languages contributed some big innovations
to the field of development programming languages.) You could
characterize the Ruby philosophy as "there's a better way to do
it" (TABWTDI).
Finally, Ruby is an "open source" development programming
language.
1.2 Where can I find out more about Ruby?
Ruby's home web site:
http://www.ruby-lang.org/en (Ruby English language home page.)
Follow the links to documentation, downloads, the Ruby
Application Archive, the Ruby mail list archives, and lots
of other interesting information.
Ruby's other major on-line documentation and links site:
http://www.rubycentral.com
Ruby FAQ:
http://www.rubycentral.com/faq/
Ruby User's Guide (introductory tutorial):
http://www.math.sci.hokudai.ac.jp/~gotoken/ruby/
(Look under "Documents" heading.)
Ruby Reference Manual:
http://www.ruby-lang.org/en/doc.html
Ruby classes, modules, and methods reference:
http://www.rubycentral.com/ref/
English language Ruby book list:
"Programming Ruby, A Pragmatic Guide"
by Dave Thomas and Andrew Hunt
Addison Wesley, 2000, ISBN: 0201710897
(Part of this book is already on the Internet; see
http://www.rubycentral.com/ref/ -- this is a great,
"absolutely must have", best-of-breed book.)
Eratta: http://www.pragmaticprogrammer.com/ruby/errata.html
Forthcoming English language Ruby book list:
"The Ruby Programming Language"
by Yukihiro Matsumoto (aka Matz) and Keiju Ishitsuka
Addison Wesley, January 12, 2001, ISBN: 0-201-71096-X
FYI: http://www.amazon.com/exec/obidos/ASIN/020171096X
Search past postings to comp.lang.ruby or the ruby-lang mail list
(which have been mirrored to each other since mid-2000):
http://www.deja.com/home_ps.shtml
(Enter comp.lang.ruby in the "forum" entry field.)
http://blade.nagaokaut.ac.jp/ruby/ruby-talk/index.shtml
2 About comp.lang.ruby.
2.1 Tell me about comp.lang.ruby.
comp.lang.ruby was officially approved in early May, 2000. Here
is the official charter:
CHARTER: comp.lang.ruby
The comp.lang.ruby newsgroup is devoted to discussions of the
Ruby programming language and related issues.
Examples of relevant postings include, but are not be limited
to, the following subjects:
- Bug reports
- Announcements of software written with Ruby
- Examples of Ruby code
- Suggestions for Ruby developers
- Requests for help from new Ruby programmers
The newsgroup is not moderated. Binaries are prohibited
(except the small PGP type). Advertising is prohibited (except
for announcements of new Ruby-related products).
END CHARTER.
2.2 Tell me about the prolific Matz poster.
Matz (aka Yukihiro Matsumoto) is the wizard who created Ruby for
us, so be nice to him. He is very busy, so be patient when asking
questions. See the Ruby home page to find out more about him and
his work. I founded comp.lang.ruby at his suggestion. Contrary to
lots of skepticism, it was approved on the first attempt, with 200
yes votes.
2.3 Tell me the posting guidelines for comp.lang.ruby.
(1) First of all, be considerate: don't be too lazy. If you are
seeking information, first make a reasonable effort to look it
up. As appropriate, check the Ruby home page, check the Ruby
FAQ and other documentation, use deja.com to search past
comp.lang.ruby postings, and so on.
(2) Make the subject line maximally informative, so that people
who should be interested will read your post and so that people
who wouldn't be interested can easily avoid it.
(a) Start with one of these keywords if appropriate:
ANNOUNCE -- new Ruby code, docs, or URLs of interest.
Bug -- report a definite bug.
Job -- advertise a Ruby-related job.
OT -- off topic.
Problem -- any sort of problem with using Ruby.
Product -- advertise a Ruby-related product.
(b) *Usefully* describe the contents of your post:
This is OK:
"How can I do x with y on z?"
"Problem: did x, expected y, got z."
"Bug: doing x with module y crashed z."
This is *NOT* OK:
"Please help!!!"
"Newbie question"
"Need Ruby guru to tell me what's wrong"
(3) Keep your content relevant and easy to follow. Try to keep
your content brief and to the point, but also try to include
all relevant information.
(a) General format guidelines:
- Use *plain* text; don't use HTML, RTF, or Word.
- Include examples from files as *in-line* text; don't
use attachments.
- PLEASE NOTE! Include quoted text from previous posts
*BEFORE* your responses. And *selectively* quote as much
as is relevant.
(b) If reporting a problem, give all the relevant information;
this isn't the psychic friends newsgroup. When
appropriate, include:
- The version of Ruby. ("ruby -v")
- The compiler name and version used to build Ruby.
- The OS type and level. ("uname -a")
- The actual error messages.
- An example (preferably simple) that produces the
problem.
(c) If reporting a bug, please copy (cc:) your post to:
mailto:ruby-bugs@ruby-lang.org
This will enter your report into the Ruby bug database.
You can browse the database at:
http://www.ruby-lang.org/cgi-bin/ruby-bugs
3. Anything else?
This FAQ was produced by Conrad Schneiker (schneiker@jump.net).
I'm interested in corrections and suggestions, but remember that
the purpose of this FAQ is to be a brief and simple introduction
for new comp.lang.ruby readers.
In closing, one of the reasons that Ruby was designed to be
relatively simple, uniform, yet very powerful was to make serious
programming (among other kinds) fun. We hope you will help us
keep comp.lang.ruby fun as well. Enjoy. :-)