[#539] A new discussion topic ;-) — Clemens Hintze <c.hintze@...>
Hi all,
[#546] Question concerning modules (1) — clemens.hintze@...
[#548] Bug: concerning Modules! — clemens.hintze@...
[#564] Ruby 1.3.7 — Yukihiro Matsumoto <matz@...>
Ruby 1.3.7 is out, check out:
[#567] New feature request! :-) — clemens.hintze@...
On 6 Aug, Yukihiro Matsumoto wrote:
Hi,
On 6 Aug, Yukihiro Matsumoto wrote:
[#590] Bug in Array#clone! — clemens.hintze@...
Hi,
Hi,
[#600] A `File' is not a `IO'????? — clemens.hintze@...
Hi,
On 10 Aug, Yukihiro Matsumoto wrote:
Hi,
Hi,
Hi,
On 11 Aug, GOTO Kentaro wrote:
Hi,
On 11 Aug, Yukihiro Matsumoto wrote:
Hi,
[#607] How to pass by `new' method of superclass? — clemens.hintze@...
[#626] Next misbehavior (sorry :-) — clemens.hintze@...
Hi,
[#634] ANN: testsupp.rb 0.1 — Clemens Hintze <c.hintze@...>
Hi,
[#637] Backtrace of SIGSEGV — Clemens Hintze <c.hintze@...>
Hi,
Hi,
On 12 Aug, Yukihiro Matsumoto wrote:
Hi,
On 12 Aug, Yukihiro Matsumoto wrote:
Hi,
[#655] Your wish is fulfilled (erhm, almost ;-) — Clemens Hintze <c.hintze@...>
Hi Gotoken,
[#667] How do I use `callcc' — Clemens Hintze <c.hintze@...>
Hi,
[#668] Way to intercept method calls? — Clemens Hintze <c.hintze@...>
Hi,
[#679] Documentation about RD? — Clemens Hintze <c.hintze@...>
Hi,
=begin
On 18 Aug, Toshiro Kuwabara wrote:
Hi,
On 18 Aug, GOTO Kentaro wrote:
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi,
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi
Hi,
Hi,
Hi Tosh and all,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
On 19 Aug, Yukihiro Matsumoto wrote:
Hi,
On 20 Aug, Toshiro Kuwabara wrote:
Hi,
On 21 Aug, Toshiro Kuwabara wrote:
Hi,
On 21 Aug, Toshiro Kuwabara wrote:
Hi,
Hi,
Hi,
On 24 Aug, Toshiro Kuwabara wrote:
Hi,
I thought people might be interested in this. Here's how I am plugging
On 31 Aug, Jonathan Aseltine wrote:
[#737] RD with multi charset — Minero Aoki <aamine@...>
Hi, I'm Minero Aoki. This is my first mail in this mailling list.
Hi,
Hi,
Hi,
Hi,
On 28 Aug, Minero Aoki wrote:
Hi,
[ruby-talk:00708] Re: Summary of discussion about RD (Re: Docum enta tion about RD?)
Hi, > > > In gotoken's idea, "((<...>))" has tree features (means). > > > (1) Reference to Headlines and Term part of DescList. > > > (2) Link with URL. > > > (3) Reference to Bibliography. > > > > Ah! Now I understand. But I would propose to use `((<...>))' only for > > (2) as <...> at least reminds me on email addresses. To refer to things > > like (1) or (2), I would propose `(([...]))', as references in written > > literature are most often denoted with [...] like in your example below > > ([HF90]). <--- Gotcha! ;-) > > > > Furthermore I think that references like (2) are other beasts as used > > in (1) and (2). > > > > Opinions? > > Well... I suppose "((<...>))" has too much feature in gotoken's idea. > It is good idea that we use different brace for reference to Element of Doc > and resource of Internet. > And do we need reference to bibliography?? I don't think so... > > > [...] > > > > > Well,so this "((<toshirok@yb3.so-net.ne.jp>))" maybe refers Headline like > > > "== toshirok@yb3.so-net.ne.jp", usage (1). > > > This is a problem of "((<mail address>))". > > > But we can regard String which contains "@" and "." and not contains /\s/ > > > as Mail Address probably. Do you think this rule "valid"? and "wished"? > > > > Why restrictive? My proposal perhaps could solve the problem, couldn't > > it? :-) > > You may be right. Excuse me, but I ask you one thing.> \cle I think that if we restrict "((<...>))" within (2) type, but even so we also have to write "((<mailto:toshirok@yb3.so-net.ne.jp>))" for mail address, because we write URL inside "((<...>))" for (2). Did you propose to restrict "((<...>))" only to mail address? I suppose using "((<...>))" for URL reference is better. "((<URL:http://www.netlab.co.jp/ruby/>))" is verbose, and using "((<...>))" only for mail-address is too restricted. --- Tosh