[#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: nil encoding as synonym for binary encoding

From: Martin Duerst <duerst@...>
Date: 2008-01-13 05:48:38 UTC
List: ruby-core #15046
At 19:44 08/01/12, Vincent Isambart wrote:
>
>On Jan 12, 2008, at 10:53 AM, Martin Duerst wrote:
>
>> This might slightly change once we introduce a third argument to
>> String#encode. This third argument, as I currently plan it, should
>> be able to express things such as "convert non-convertibles to
>> a replacement character" or "simply drop non-convertible data"
>> or so.
>
>
>Instead (or in addition to) this third argument, what about having the  
>String#encode function taking a block?

That's also planned. But a third argument can be much faster for
the simple cases, that's why I don't want to exclude it.

>I haven't thought at it a lot, but something like this could be useful:
>- to replace unknown characters with '?'
>str.encode('UTF-8') { '?' }
>- to strip the unknown characters
>str.encode('UTF-8') { '' }
>- to trancode from a mix of UTF-8 and ISO-8859-1 to ISO-8859-1 (yes  
>that may sound strange but I've seen cases when it may appear with  
>badly managed data)
>str.encode('ISO-8859-1', 'UTF-8') { |s| s }
>
>(to may everything simpler I did not take into account the encoding of  
>the string returned by the bloc, checking it may be a good thing, I do  
>not know)
>
>You may even want to be able to control if the block is called with  
>either each unknown byte or each sequences of unknown bytes. Giving  
>the position in the start string to the lock may be also a good idea.
>
>I'm not sure this idea could have any useful use except in the case of  
>data in mixed encodings (and I'm note even sure if this is common or  
>not), and it probably needs some more thought, but it was just an idea  
>that crossed my mind and seemed more 'Ruby-like' than just an  
>additional parameter. The encode function may of course be made to  
>support both the additional parameter and the bloc.

It's definitely Ruby-like, and there are quite a few use cases.
The one I'm thinking about most is converting non-convertible
characters to escapes of various kinds. I have thought about
quite a few of the cases you mention above, but I have to
think through your 'convert from mixed encoding' case a bit
more.

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

Prev Next