[#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: Martin Duerst <duerst@...>
Date: 2008-01-25 08:47:41 UTC
List: ruby-core #15209
At 11:38 08/01/25, Jim Cropcho wrote:
>Does anyone think that it is a good idea to include similar methods for japanese/east asian languages?

I don't think so. Ruby doesn't localize it's method names.
If things are clear in simple English (as they are in your case),
it should be fine.

Regards,   Martin.


>I'm not too familiar with japanese/localization in ruby-core. Would that go in the same module, or a different one? 
>
>Any naming scheme that helps visualize is good. How can we make this work best for the great number of locales?
>
>2008/1/24 Jim Cropcho <<mailto:jim.cropcho@gmail.com>jim.cropcho@gmail.com >:
>>Here is the newest patch. It creates a module called Temporal which contains functionality useful to classes which define temporal objects, such as dates and times. However, its intended scope is *not* limited to object comparison. It is handy in this regard, though, because it addresses differences between languages, as several in this thread have noted.
>>
>>The module is added to the compilation configuration, and unit tests are included, all of which pass. The module is included in the classes Time and Date (and DateTime, via extension). 
>>
>>The module does not include the methods past? and present?, as intended, because the means of determining "now" is different even at the conceptual level between temporal classes. For example, "now" to Time is the number of microseconds after epoch, but "now" to Date is the current calendar date. It is my opinion that past?/future? functionality should be implemented at the class level. 
>>
>>Please give my concept and source code consideration for being entered into the ruby core, and suggest modifications/additions at will.
>>
>>
>>Jim Cropcho
>>
>>2008/1/23 Jim Cropcho < <mailto:jim.cropcho@gmail.com>jim.cropcho@gmail.com>:
>>
>>>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 <http://ruby-doc.org/core/classes/Comparable.html>Comparable 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. <http://ruby-doc.org/core/classes/Comparable.html>Comparable uses <=> to implement the conventional comparison operators (<, <=, ==, >=, and >) and the method <http://ruby-doc.org/core/classes/Comparable.html#M007548>between?.
>>>
>>>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 <<mailto:mblondel@rubyforge.org> mblondel@rubyforge.org >:
>>>>Hi,
>>>>
>>>>2008/1/23, Martin Duerst < <mailto:duerst@it.aoyama.ac.jp>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


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     


In This Thread