[#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: Draft of some pages about encoding in Ruby 1.9

From: Martin Duerst <duerst@...>
Date: 2008-01-12 08:31:45 UTC
List: ruby-core #15034
At 02:38 08/01/11, Yukihiro Matsumoto wrote:
>Hi,
>
>In message "Re: Draft of some pages about encoding in Ruby 1.9"
>    on Fri, 11 Jan 2008 02:22:08 +0900, "Ujwal Reddy Malipeddi" 
><ujwalic@gmail.com> writes:
>
>|I think  the document assumes that the terminal/console supports
>|various encoding and the current terminal font has glyphs to represent
>|the characters
>
>Ruby does not handle glyphs nor fonts.
>
>|does 1.9 support other BOMs?
>
>No, Ruby does not handle BOM.  They are evil.  The only exception is
>UTF-8 BOM at the beginning of Ruby programs.
>
>|Encoding
>|* UTF-8
>
>Yes.
>
>|* UTF-16 Big Endian
>|* UTF-16 Little Endian
>|* UTF-32 Big Endian
>|* UTF-32 Little Endian
>
>Yes, in the trunk.

Conversions (String#encode) should be added over the weekend.
[well, after I have sorted through all the recent emails :-(]

>|* UTF-7
>
>Not yet, but possible.  Ruby allows user defined encoding.

This one is discouraged for quite a while, because it's
not really a character encoding, more something like base64.
But I guess eventually, somebody will implement at least
conversion from and to this beast.

>|* UTF-EBCDIC
>
>Ruby programs must be in ASCII compatible encoding.  The encoding
>itself can be supported, I guess.  We've never tried non ASCII
>compatible encoding before.

Same here, conversion might be implemented in a few months or years,
but don't expect that soon, and don't expect anything else.

>|* SCSU
>|* BOCU-1
>
>I don't know these.

Both are in some way closer to compression methods than to
character encodings, but tailored for Unicode. They are very
definitely not suited for internal processing. Same answer as
just above.

>|which version of Unicode is supported in 1.9?
>
>Ruby does not cover version sensitive area of Unicode (character
>repertoire etc) yet.  It should be handled by external library,
>e.g. unicode gem.

Not exactly true. Oniguruma supports a lot of Unicode properties.
All the data is in unicode.c (currently enc/unicode.c).
Something like the following should actually work, independent
of your local settings:
> ruby -e 'puts "\u3042" =~ /\p{Hiragana}/u'
0

(U+3042 is Hiragana a (あ)).

The tables in unicode.c are in a derived form that makes it rather
difficult to figure out which version they are based on, but a
rough comparison between
http://www.unicode.org/Public/UNIDATA/DerivedAge.txt
and init_code_range_array in enc/unicode.c makes Version 4.1.0
the best guess.

Regards,    Martin.







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