From: Robert Klemme <shortcutter@...>
Date: 2006-05-14T19:27:12+09:00
Subject: Re: An inherent mismatch when creating dynamic classes

2006/5/12, Juergen Strobel <strobel@secure.at>:
> On Sat, May 13, 2006 at 12:20:52AM +0900, Eli Bendersky wrote:
> > IMHO it's a mismatch because when I want to create a class dynamically
> > in some method, I just want to give it a Name like any other class,
> > beginning with an uppercase letter. But I can't, because it is
> > considered a dynamic constant assignment. So I'm forced to name it
> > against the Ruby convention (or use const_set)
>
> But dynamically created classes are not constant, so just assign them to
> a (lowercase initialled) variable and pass it around. It is *you* wanting
> to assign something dynamically created to a constant that's the problem.
> Why does your dynamically created class need a constant name?

Exactly!  Thanks for voicing my concerns much better than I did.
Adding to that, what's the use of a class name of a dynmic created
class?  The name won't be known to other parts of the code beforehand
so it cannot be used for referencing the class.

Kind regards

robert

-- 
Have a look: http://www.flickr.com/photos/fussel-foto/