[#14696] Inconsistency in rescuability of "return" — Charles Oliver Nutter <charles.nutter@...>

Why can you not rescue return, break, etc when they are within

21 messages 2008/01/02
[#14699] Re: Inconsistency in rescuability of "return" — Gary Wright <gwtmp01@...> 2008/01/02

[#14738] Enumerable#zip Needs Love — James Gray <james@...>

The community has been building a Ruby 1.9 compatibility tip list on

15 messages 2008/01/03
[#14755] Re: Enumerable#zip Needs Love — Martin Duerst <duerst@...> 2008/01/04

Hello James,

[#14772] Manual Memory Management — Pramukta Kumar <prak@...>

I was thinking it would be nice to be able to free large objects at

36 messages 2008/01/04
[#14788] Re: Manual Memory Management — Marcin Raczkowski <mailing.mr@...> 2008/01/05

I would only like to add that RMgick for example provides free method to

[#14824] Re: Manual Memory Management — MenTaLguY <mental@...> 2008/01/07

On Sat, 5 Jan 2008 15:49:30 +0900, Marcin Raczkowski <mailing.mr@gmail.com> wrote:

[#14825] Re: Manual Memory Management — "Evan Weaver" <evan@...> 2008/01/07

Python supports 'del reference', which decrements the reference

[#14838] Re: Manual Memory Management — Marcin Raczkowski <mailing.mr@...> 2008/01/08

Evan Weaver wrote:

[#14911] Draft of some pages about encoding in Ruby 1.9 — Dave Thomas <dave@...>

Folks:

24 messages 2008/01/10

[#14976] nil encoding as synonym for binary encoding — David Flanagan <david@...>

The following just appeared in the ChangeLog

37 messages 2008/01/11
[#14977] Re: nil encoding as synonym for binary encoding — Yukihiro Matsumoto <matz@...> 2008/01/11

Hi,

[#14978] Re: nil encoding as synonym for binary encoding — Dave Thomas <dave@...> 2008/01/11

[#14979] Re: nil encoding as synonym for binary encoding — David Flanagan <david@...> 2008/01/11

Dave Thomas wrote:

[#14993] Re: nil encoding as synonym for binary encoding — Dave Thomas <dave@...> 2008/01/11

[#14980] Re: nil encoding as synonym for binary encoding — Gary Wright <gwtmp01@...> 2008/01/11

[#14981] Re: nil encoding as synonym for binary encoding — Yukihiro Matsumoto <matz@...> 2008/01/11

Hi,

[#14995] Re: nil encoding as synonym for binary encoding — David Flanagan <david@...> 2008/01/11

Yukihiro Matsumoto writes:

[#15050] how to "borrow" the RDoc::RubyParser and HTMLGenerator — Phlip <phlip2005@...>

Core Rubies:

17 messages 2008/01/13
[#15060] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Eric Hodel <drbrain@...7.net> 2008/01/14

On Jan 13, 2008, at 08:54 AM, Phlip wrote:

[#15062] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Phlip <phlip2005@...> 2008/01/14

Eric Hodel wrote:

[#15073] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Eric Hodel <drbrain@...7.net> 2008/01/14

On Jan 13, 2008, at 20:35 PM, Phlip wrote:

[#15185] Friendlier methods to compare two Time objects — "Jim Cropcho" <jim.cropcho@...>

Hello,

10 messages 2008/01/22

[#15194] Can large scale projects be successful implemented around a dynamic programming language? — Jordi <mumismo@...>

A good article I have found (may have been linked by slashdot, don't know)

8 messages 2008/01/24

[#15248] Symbol#empty? ? — "David A. Black" <dblack@...>

Hi --

24 messages 2008/01/28
[#15250] Re: Symbol#empty? ? — Yukihiro Matsumoto <matz@...> 2008/01/28

Hi,

Re: [PATCH] Friendlier methods to compare two Time objects

From: "Jim Cropcho" <jim.cropcho@...>
Date: 2008-01-24 02:45:02 UTC
List: ruby-core #15193
A new thought:

> The way that the <=> method is rewritten for Time, it is
> optimized (as far as I can tell) to evaluate conditions
> based on nanoseconds only when equality cannot be
> determined via seconds. I may be misreading that.
>
> Conversely, Time inherits its > and < methods from its superclass,
> so surely those optimizations in <=> do not exist, and creating
> aliases would yield less-optimized code. Also, in the other classes
> where I add this functionality, current techniques to optimize
> comparisons will be reimplemented using the local methodology.

from the rdoc for compar.c:

The Comparable <http://ruby-doc.org/core/classes/Comparable.html> mixin is
used by classes whose objects may be ordered. The class must define
the <=>operator, which compares the receiver against another object,
returning -1,
0, or +1 depending on whether the receiver is less than, equal to, or
greater than the other object.
Comparable<http://ruby-doc.org/core/classes/Comparable.html>uses
<=> to implement the conventional comparison operators (<, <=, ==, >=, and >)
and the method between?<http://ruby-doc.org/core/classes/Comparable.html#M007548>
.

I am now writing a Mixin called Temporal which will be included in the Time
, Date and DateTime classes, and will contain the instance methods

*before?(some_time)
*after?(some_time)
*future?(time = Time.now)
*past?(time = Time.now)

I have the tests written and skeleton code to compile and include the module
where necessary. I hope to be finished tomorrow.

2008/1/23 Mathieu Blondel < mblondel@rubyforge.org >:

> Hi,
>
> 2008/1/23, Martin Duerst < duerst@it.aoyama.ac.jp>:
>
> > There is even some cultural dependency here. In Japanese, for example,
> > the past is higher than the future, time flows down,
>
> And in Chinese as well. For example:
>
> 下个星期 = next week, lit. below week
> 上个星期 = last week, lit. above week
>
>
> Mathieu
>
>

In This Thread