<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: Safe pattern for creating new root classes</TITLE>
</HEAD>
<BODY>
<BR>
<BR>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Lex Spoon [<A HREF="mailto:lex@cc.gatech.edu">mailto:lex@cc.gatech.edu</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Friday, March 24, 2000 12:20 PM</FONT>
<BR><FONT SIZE=2>> To: squeak@cs.uiuc.edu</FONT>
<BR><FONT SIZE=2>> Subject: RE: Safe pattern for creating new root classes</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>[snip]</FONT>
</P>
<P><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > Or we could dynamically load the superclass...</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Where would you load it from? The problem is when you say:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> A subclass: B</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> and A doesn't exist (yet). Currently, B ends up as a new root class,</FONT>
<BR><FONT SIZE=2>> which probably wasn't intended. It's especially problematic because</FONT>
<BR><FONT SIZE=2>> loading a future version of A, will not correct B's definition.</FONT>
</P>
<P><FONT SIZE=2>If we had dynamically loaded classes, like a certain other language,</FONT>
<BR><FONT SIZE=2>we would first try to load A. I'm assuming that this might tie into</FONT>
<BR><FONT SIZE=2>some of the work that SqC is in the middle of.</FONT>
</P>
<P><FONT SIZE=2>-david</FONT>
</P>
<P><FONT SIZE=2>PS - Is my mail reader sending out MIME again? I got a new machine</FONT>
<BR><FONT SIZE=2>yesterday with Outlook 2000 and I have been through every menu I can</FONT>
<BR><FONT SIZE=2>find and it looks like its supposed to be sending plain text. The </FONT>
<BR><FONT SIZE=2>Format menu on this message claims that I'm in plain text.</FONT>
</P>
</BODY>
</HTML>