[#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: Symbol#empty? ?

From: Gary Wright <gwtmp01@...>
Date: 2008-01-28 17:58:04 UTC
List: ruby-core #15278
On Jan 28, 2008, at 11:42 AM, Dave Thomas wrote:
> Let's assume that I know what a Ruby Hash is... :)

Of course, which is why your comment 'a Hash object not to_hash' was  
confusing to me.  You were describing a hash function, and not a Hash  
object.  I didn't mean to imply that you didn't know what you were  
talking about but instead that I didn't know what you were talking  
about. :-)

> If you really want to map arbitrary strings to some other value,  
> then you can use a Hash to manage that
>
> class StringToInt
>     # ....
> end

And I have to add String#to_myint and Fixnum#to_mystring so that I  
can pass around the integer to use for comparisons but still be able  
to map back to the string when needed.  But I've got no way to  
distinguish between a regular old integer and an integer that is  
really a 'symbol'.  I've thrown away all the benefits of symbols  
being objects rather than just interpretations of integers.

I'm not arguing that it is impossible to implement 'pure-symbol'  
semantics without using Symbol.  That wouldn't be hard at all.  No  
one does that of course because for all practical purposes that is  
what most programmers view Symbol as already, which is why people are  
surprised when they see that
           :"!" == :"!@"
is true.

If you view Symbol as something very specific to the reflection  
capabilities of Ruby, then I understand why you might want to  
restrict the String<->Symbol mapping.  But if you are looking at it  
as a more abstract hashing mechanism with syntactic sugar, then there  
doesn't seem to be a reason to cripple the abstraction to be so  
specific to Ruby's notion of an identifier.

But still:
> This is somewhat academic.  In the real world there are three options:
>
>   a) leave Symbol alone with its current RubyInternalSymbol  
> semantics ("@+"...)
>   b) make Symbol 'pure' and change Ruby's internals
>   c) make Symbol 'strict' and break lots of programs
>
> I can live with 'a', would prefer 'b', and think 'c' is a bad idea.





In This Thread

Prev Next