[#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: Dave Thomas <dave@...>
Date: 2008-01-10 15:41:37 UTC
List: ruby-core #14931
>
Martin:

Thanks for taking all the time to comment on this. I really appreciate  
it. I have a couple of questions based on stuff you're raised.


> In your text, you always use SJIS, whereas the canonical
> name is SHIFT_JIS. I suggest you use the later more,
> and you mention that some encodings have aliases, and
> that all encoding names can be written in any case
> you want.

Do you mean in the body text, or in the encoding: sjis inline?

> For the association between objects and encodings, you
> often use 'encoded'. In many if not all instances in the text,
> this suggests that Ruby is actually doing some encoding,
> where Ruby simply *labels* the object (string,...).
> Using the word 'label' instead of 'encode' will help
> getting the right message across.

Thanks, I'll check these

>
>
> p. 1: the PDF writing library: case typo

I'm not sure I understand.

> p.2, bottom, you say that ASCII-8BIT treats bytes 128 to 255
> as additional letters. This is confusing, because it suggests
> that e.g.
>    "a\xCCbc" ~= /^\w*$/
> would return true, which isn't the case.

Good point

> p. 5: Example 12 may stop to work in the near future, because
> on the Japanese list, it was pointed out that the IANA charset
> registry has 'ascii' as an alias of 'us-ascii', and therefore
> Ruby should do this too, but currently it's an alias of ASCII-8BIT.
> ASCII-8BIT is, more or less as you describe it,
>    lower bytes -> ASCII
>    upper bytes -> some data, seen as bytes
> US-ASCII, on the other hand, is
>    lower bytes -> ASCII
>    upper bytes -> disallowed
> In that thread, Matz pointed out that probably nobody will notice.
> I then said that I probably woudn't have noticed, but now that I
> know, I feel responsible to request a change (or change it myself)
> because I'm also an expert reviewer for that registry.
> [I also said that I don't think that everything in that registry
> should be followed slavishly, but that unnecessary and arbitrary
> differences should be avoided.]
> I haven't yet heard back from Matz or others on that point, but
> I'm inclined to go ahead and change it, and that would affect
> example 12, and maybe other parts of your text.

I'll make that change. However, two questions: why don't encodings  
like us-ascii and iso-8859-1 appear in Encoding.list?

Also, is there a programmatic way to list the aliases for an encoding?

Dave

In This Thread