[#2529] concerns about Proc,lambda,block — "David A. Black" <dblack@...>
Hi --
>>>>> "D" == David A Black <dblack@wobblini.net> writes:
Hi --
Hi,
On Tue, 2 Mar 2004 08:44:25 +0900, Yukihiro Matsumoto wrote:
Hi,
On Wednesday, 3 March 2004 at 8:00:09 +0900, Yukihiro Matsumoto wrote:
Hi,
Hi,
On Wed, Mar 03, 2004 at 07:51:10AM +0900, Yukihiro Matsumoto wrote:
Hi,
On Thu, 4 Mar 2004, Yukihiro Matsumoto wrote:
Hi,
[#2575] Comment football being played... with lib/test/unit.rb — Nathaniel Talbott <nathaniel@...>
[Resent because I accidentally signed it the first time]
[#2577] problem with Net::HTTP in 1.8.1 — Ian Macdonald <ian@...>
Hello,
Hi,
[#2582] One more proc question — Dave Thomas <dave@...>
Sorry about this... :)
Hi,
On Friday, 5 March 2004 at 12:52:15 +0900, Yukihiro Matsumoto wrote:
Hi,
[#2588] Duck typing chapter — Dave Thomas <dave@...>
I've posted a rough first pass at a chapter about duck typing (and
[#2606] Thought about class definitions — Dave Thomas <dave@...>
If we allowed
[#2628] YAML complaint while generating RDoc — Dave Thomas <dave@...>
With the latest CVS, I get
[#2640] patch to tempfile.rb to handle ENAMETOOLONG — Joel VanderWerf <vjoel@...>
[#2644] RDoc proporsal — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp>
Hi, rubyists.
[#2646] Problems rdoc'ing cvs... — Hugh Sasse Staff Elec Eng <hgs@...>
I have just done
On Friday, March 12, 2004, 4:15:42 AM, Dave wrote:
On Fri, 12 Mar 2004, Dave Thomas wrote:
[#2661] Pathological slowdown in 1.8 — Ryan Davis <ryand@...>
Hi all,
[#2697] lib/ruby/1.9/yaml.rb:193: [BUG] Segmentation fault — Mauricio Fern疣dez <batsman.geo@...>
Mauricio Fern疣dez wrote:
On Sun, Mar 28, 2004 at 09:42:42AM +0900, why the lucky stiff wrote:
[#2703] Proposed patch to add SSL support to net/pop.rb — Daniel Hobe <daniel@...>
This patch adds support to Net::POP for doing POP over SSL. Modeled on how
This is v2 of the patch. Cleaned up a bit and added some more docs.
v3 of the patch:
Hi,
I agree that there are a lot of arguments to #start, but I think it is the
On Tue, 30 Mar 2004 16:24:17 +0900, Daniel Hobe wrote:
On Wed, 31 Mar 2004 13:27:31 +0900, Daniel Hobe wrote:
On Tue, Mar 30, 2004 at 04:05:06PM +0900, Minero Aoki wrote:
[#2709] typos in lib/singleton.rb — Ian Macdonald <ian@...>
Hello,
[#2713] more spelling and grammar fixes — Ian Macdonald <ian@...>
Hello,
> Hello,
Hi,
Re: Duck typing chapter
On Mar 5, 2004, at 17:44, Warren Brown wrote:
> One thing that stuck out to me is that after explaining that in
> Ruby
> the class is not the type, the class Roman tests the class of its
> parameters (i.e. "if Integer === other"). In this case you could (and
> probably will) argue that the class *is* the type, but this should
> probably be specifically stated to the reader to avoid confusion.
Well, I think I'd probably say that we're interested in the class here,
not the type. The classes contain the implementation of methods sych as
'+', are we're trying to determine is we have compatible a compatible
receiver and argument for addition. So I'm not really interested in the
type as much as I am in the implementation.
Does that make sense?
>
> I'm sure you'll find all of the easy typos, but there is a subtle
> one in the Roman#initialize method (no not the "muts" one). The error
> message should say "<= #{MAX_ROMAN}", not "< #{MAX_ROMAN}".
>
Oh! Good catch.
> The only other thing that struck me as odd was the assumption in
> Roman#coerce that any parameter that is not a Fixnum should be
> converted
> to a Float. This seems a bit simplistic, especially with Bignum as a
> built-in class, and would seem to preclude using some other
> Integer-like
> class (Chinese number?). Perhaps a check for a to_int method would be
> more appropriate?
>
This whole example is screwy, but let me tell you my initial reasoning.
If the argument is a Roman number, then the result might be a Roman
number.
If the result is a Fixnum, then the result might be a Roman number
But is the argument is a bignum or anything else, the result can't be a
Roman number (because bignums would be too big).
I can't test for to_int, because that would lose precision (Float
supports to_int, which I'm going to post about separately).
Having said that, the more I look at this code, the less I like it.
Roman numbers are representations, and don't really support arithmetic
directly.
Time for a new example, methinks
Cheers
Dave