[#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-12 09:43:09 UTC
List: ruby-core #15035
At 01:31 08/01/12, Dave Thomas wrote:
>
>On Jan 11, 2008, at 10:18 AM, Michal Suchanek wrote:
>
>> For one, somebody suggested that
>> "aaa".force_encoding(Encoding::BINARY)[0] makes no sense as you do not
>> know how to break into characters. Perhaps byte indexing should be
>> allowed then?
>
>But what would you return? An ASCII character? Or an integer? I'd  
>strongly argue that for a binary byte sequence, an integer is the  
>correct return value.

Well, a binary byte sequence of length one is what would be returned
now, and I don't think that's too bad.

>> Then if you want to find out whether there is "GIF"  at the start you
>> cannot because "GIF" is an ASCII string but your string is
>> unknown-binary. Or should the binary string allow byte comparison
>> (searching, ..) with strings of any encoding (even ecbdic or whatever
>> it is called)? If there is no searching these byte buffers are pretty
>> useless, right?
>
>I think that the GIF example is a bad one. A GIF is not an character  
>string. It's a sequence of bits where someone decided to stick a  
>particular pattern into the first 24 of them to aid in identification.  
>It's no different to having a particular bit pattern framing an SDLC  
>header, or a certain bit sequence encoding the start of a relocation  
>record in a .o file.

There were some similar discussions when working on the URI and IRI
specs (RFC 3986 and RFC 3987). In the simple case, with an URI like
   http://www.ruby-lang.org/en/downloads/
these are ASCII letters are bytes are ASCII letters are bytes, and
nobody really sees the distinction or has to care.
But specs need to define these things so that they work even in
e.g. on EBCDIC servers and the like. So to be exact, and 'e'
in an URI actually means "send the byte value corresponding to
ASCII-encoded character 'e'". Therofore, you can also write the
above e.g. as http://www.ruby-lang.org/%65n/downloads/.

>However, to answer the question, it seems to me that the safest way  
>would be to work at the lowest common denominator:
>
>   first_three = buffer[0,3]
>   if first_three == "GIF".force_encoding("binary")

I wouldn't see too much of a problem to allow this to
be written simply

   if first_three == "GIF"

Neither your more explicit version above nor mine will
work with EBCDIC, anyway, but then Matz isn't plannig
Ruby to work on an EBCDIC system, either.
   


>My point is that a true binary bit sequence by definition is not  
>ASCII. We're matching bit patterns, not characters.

Yes indeed. But we can use ASCII characters as a convenient
shortcut for some byte values if we agree that we define things
that way.

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