KCP 64-90 - comments, questions and approvals

Doug Way dway at riskmetrics.com
Tue Jul 1 04:28:53 UTC 2003


On Thursday, June 26, 2003, at 10:01 AM, Daniel Vainsencher wrote:

> Doug, KCP doesn't show up in BFAV yet, hence this heads up. This
> approves almost all the outstanding KCP stuff.
>
> To business - I really like the way the new deprecation system works
> out. People deprecating all sorts of protocols should really be using
> this. Of course for every deprecation we do, eventually, we'll have to
> remove the deprecated code - maybe we should do this at the beginning 
> of
> each alpha?

That sounds right.  We can simply check for all senders of the 
deprecatedExplanation/deprecated:explanation: and then delete those 
methods.

> ...
> One place where I think things should be done differently (we talked
> about this before -) 64.
>
> Everything else, that is, 67, 68, 69, 70, 71, 76, 78, 83, 84, 85, 87,
> 88, 90 - approved.

So is this a reasonable stopping point?  If so, I can go ahead and 
incorporate these. (excluding 64 for now)

Here's the list if anyone else is curious (see 
http://minnow.cc.gatech.edu/squeak/3257 )

KCP-0090-SpaceTally.cs
KCP-0088-FixChangeSet.cs
KCP-0087-MovefullScreenModeToDisplayScreen.cs
For the changes 85 and 84. You will prompted to know if SystemChanges 
shouldmarked as undeclared. Then one deprecated method will be 
executed: this is normal because the changeset is changing the exact 
method that is loading the changesets. So just proceed.
KCP-0085-MoveToChangeSet.cs
KCP-0084-ChangeSetCurrentFixed.cs
KCP-0083-NewBeepENG.cs
KCP-0078-fixDeprecationMechanism.cs
KCP-0076-ValidateSubclassFormatFix.cs
KCP-0071-mvDefaultSelectorForMethod.cs
KCP-0070-FixSmalltalkReferenceInBrowser.cs
KCP-0069-FixChangeSorter.cs
KCP-0068-Imports.cs
KCP-0067-beep.cs
KCP-0064-PictReaderClass.cs

- Doug Way



More information about the Squeak-dev mailing list