Yukihiro Matsumoto writes:
> Hi,
> 

Hi matz,

[...]

> It used to give a error before.  But it was not good for

[...]

> After some consideration, I felt even warnings are irritating, so I
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> decided to let redefining constants upto programmers' responsibility.
> I know they aren't really constants by this, but I think it's OK for
> everyday use.

Does that mean, we will not get any warning if this happen in
future??? In Ruby 1.4.3 it is:

   /home/hintze$ ruby
   A = 12
   A = 11
   ^D
   -:2: warning: already initialized constant A
   /home/hintze$ ruby -v
   ruby 1.4.3 (1999-12-08) [sparc-solaris2.7]

Forgive me, if I have misunderstood. But please let, at least, the
warning show me that some constant were reinitialized. Otherwise I
mistakenly could overwrite some constants of certain libraries without
indication of my fault! Imagine how many libraries dealing with some
kind of communication could have a constant PORT or DEFAULT_PORT?

> 
> 							matz.

\cle