[#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,

Does Symbol#next work unter Ruby 1.9 with intention or by accident?

From: Wolfgang Nádasi-Donner <ed.odanow@...>
Date: 2008-01-13 15:30:39 UTC
List: ruby-core #15049
Dear language designers and developers!

Yesterday I recognized a feature in Ruby 1.9.0-0, that didn't
exist in Ruby 1.8 - Symbol#next...

C:\Dokumente und Einstellungen\wolfgang>irb
irb(main):001:0> :_1.next
NoMethodError: undefined method `next' for :_1:Symbol
         from (irb):1
irb(main):002:0> exit

C:\Dokumente und Einstellungen\wolfgang>irb190
irb(main):001:0> :_1.next
=> :_2
irb(main):002:0> exit

This can make a special application very simple, because now
ranges of symbols can be defined...

irb(main):001:0> [*:__0..:__9]
=> [:__0, :__1, :__2, :__3, :__4, :__5, :__6, :__7, :__8, :__9]

Is the existence of Symbol#next done by intention or is it only
available by accident and will be removed later on? -  I would like
to know this, because I have an application where I need such a
functionality and I mus build it myself.

In addition, if it is the by intention, I must unfortunately
report an error...

C:\Dokumente und Einstellungen\wolfgang>irb190
irb(main):001:0> [*:__0..:__19]
=> [:__0, :__1]
irb(main):002:0> [*:__0..:__29]
=> [:__0, :__1, :__2]
irb(main):003:0> [*((:__0)..(:__10))]
=> [:__0, :__1]
irb(main):004:0> :__10.to_s
=> "__10"
irb(main):005:0> [*:__0..:__99]
=> [:__0, :__1, :__2, :__3, :__4, :__5, :__6, :__7, :__8, :__9, :__10, :__11, 
:__12, :__13, :__14, :__15, :__16, :__17,
:__18, :__19, :__20, :__21, :__22, :__23, :__24, :__25, :__26, :__27, :__28, 
:__29, :__30, :__31, :__32, :__33, :__34, :
__35, :__36, :__37, :__38, :__39, :__40, :__41, :__42, :__43, :__44, :__45, 
:__46, :__47, :__48, :__49, :__50, :__51, :_
_52, :__53, :__54, :__55, :__56, :__57, :__58, :__59, :__60, :__61, :__62, 
:__63, :__64, :__65, :__66, :__67, :__68, :__
69, :__70, :__71, :__72, :__73, :__74, :__75, :__76, :__77, :__78, :__79, :__80, 
:__81, :__82, :__83, :__84, :__85, :__8
6, :__87, :__88, :__89, :__90, :__91, :__92, :__93, :__94, :__95, :__96, :__97, 
:__98, :__99]
irb(main):006:0> [*:__0..:__59]
=> [:__0, :__1, :__2, :__3, :__4, :__5]
irb(main):007:0> [*:__0..:__9]
=> [:__0, :__1, :__2, :__3, :__4, :__5, :__6, :__7, :__8, :__9]

...because it doesn't work as expected.

Wolfgang N叩dasi-Donner

In This Thread

Prev Next