[Seaside-dev] Two minor implementation questions

[Roger Whitney]

The change is probably not worth the effort. I will add a note in the  
class comment explaining the issue.

On Oct 16, 2007, at 4:13 AM, Lukas Renggli wrote:


>
>> The second place is in WASystemConfiguration. This class is a
>> singleton. There is a single instance of the class stored in a class
>> instance variable. This does not seem to make sense. First of all
>> WASystemConfiguration and its parent class WAConfiguration have no
>> state. Secondly WASystemConfiguration is an abstract class. So there
>> does not seem any need for the singleton.
>
> There are a couple of subclasses. Every subclass has its own variable
> #instance to store its specific singleton instance. It is important to
> always have the same instance, because #= is not overridden. We could
> probably get rid of this singleton behavior by overriding #= and
> checking for the same class, but I don't know if this is worth the
> change?
>
> Lukas
>
> -- 
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>



----
Roger Whitney              Department of Computer Science
whitney at cs.sdsu.edu        San Diego State University
http://www.eli.sdsu.edu/   San Diego, CA 92182-7720