From: "James F.Hranicky" Date: 2002-06-12T09:19:46+09:00 Subject: Re: ruby-dev summary 17252-17356 On Tue, 11 Jun 2002 13:20:03 +0900 "Minero Aoki" wrote: > * Backward compatibility takes precedence over all. > > * The problem is that block localization may be broken with > name collision between inside of the block and the outside. > > * It is not true that ruby does not have block local variables. > The problem is that local variables does NOT shadows outer > local variables. Should we perhaps take a vote and see how many folks have ruby programs that depend on block parameters referencing outer variables? I've always treated block variables as block local -- perhaps breaking backwards compatibility won't have such a huge impact. ---------------------------------------------------------------------- | Jim Hranicky, Senior SysAdmin UF/CISE Department | | E314D CSE Building Phone (352) 392-1499 | | jfh@cise.ufl.edu http://www.cise.ufl.edu/~jfh | ----------------------------------------------------------------------