ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> ruby-talk
ruby-talk
Re: Subclassing Struct.new
by Yukihiro Matsumoto other posts by this author
Feb 28 2006 11:45PM messages near this date
Re: Subclassing Struct.new | Re: Subclassing Struct.new
Hi,

In message "Re: Subclassing Struct.new"
    on Wed, 1 Mar 2006 16:28:37 +0900, "Minkoo Seo" <minkoo.seo@[...].com>  writes:

|This make sense, but
|
|>  | def baz
|>  |   n # variable - Do we really need this uninitialized variable access?
|>  |   n = 3
|>  |   n 
|>  | end

For example, in cases like this:

  def foobar(ary)
    # we need to "declare" a variable here under the current behavior,
    # but no longer under the new behavior
    ary.each do |elem|
       if some_condition_on_elem(elem)
          found = elem     # "found" will be available during whole #foobar.
          break
       end
    end
    some_work_with_found_elem(found)
    return found
  end

							matz.
Thread:
Minkoo Seo
Chiaro Scuro
Minkoo Seo
Yukihiro Matsumoto
Mark Wilden
Markus Werner
Chiaro Scuro
Minkoo Seo
Minkoo Seo
Hal Fulton
mental
Ross Bamford
mental
Ross Bamford
Chiaro Scuro
Ross Bamford
Chiaro Scuro
Minkoo Seo
Chiaro Scuro
mental
Chiaro Scuro
mental
Yukihiro Matsumoto
Caleb Clausen
Yukihiro Matsumoto
Caleb Clausen
MenTaLguY
Yukihiro Matsumoto
gwtmp01
Chiaro Scuro
mental
Chiaro Scuro
mental
Logan Capaldo
Pit Capitain

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved