ContextCleanupPlus-ajh (was: Re: KCP & 3.6)

> >4 Anthony runtime enhancements (split in two - fixes and closures)

There are two packages: ContextCleanupPlus-ajh.zip and ClosureCs-ajh.zip. 
ContextCleanupPlus cleans up contexts, exceptions, and related classes.  You
can think of it as part of KCP.  I have used it for about a year in my image,
and after a few minor updates here and there, things are running very smoothly.
 I would encourage people to test it just by loading it and going about their
normal business.  Normal operation will test its low-level changes.

> What about the SmaCC license issue?

ContextCleanupPlus does not depend on SmaCC, only ClosureCs does which we can
be considered after ContextCleanupPlus.  ClosureCs depends on
ContextCleanupPlus but not vice versa.

> Anthony, for some reason includes in this package myriad changes to
> existing classes.

Of course, cleanup involves changes to existing classes.  If you're talking
about the additional protocol I've added to general classes, below are the
detailed explanations.  I think you will agree they a reasonable, and truly
belong as class extensions rather than in user classes where they would be
tedious and less reusable.  I would not be afraid to add these new protocols
especially since they can't affect any existing code.  Note, many of the users
are in ClosureCs and not in ContextCleanupPlus itself.

Object>>literalEqual: - Do the receiver and argument represent the same
literal.  Note, two objects can be = but not literalEqual: as in 'anthony' =
#anthony, but ('anthony' literalEqual: #anthony) not.

Boolean>>asBit - Return 1 for true, 0 for false.

Class>>becomeClass: otherClass - Become forward the other class and fix up the
global dictionary and system organization as well.

Collection>>collectArray: - Same as collect: except always return an array.

CompiledMethod>>headerDescription - Prints out all the components of the header
(numArgs, numLiterals, etc) in a readable format.

LargePositiveInteger>>as31BitSmallInt - Keep my 31 bits the same but put them
in a SmallInt.

Number>>extend: - Like #to: except designate the length instead of the last.

OrderedCollection>>bottom,top,pop,push,etc. - stack protocol.

SequenceableCollection>>allButFirstDo:,allButLastDo:,atLast:,atLast:put:
,copyGrowBy:copyWithFirst:,detectIndex:,reverseDetect:,slide:by:,with:wi
thIndexDo: - Additional methods that are similar to other methods that already
exist and should be part of the protocol because they are useful.  I bet many
of these have been needed in the past but were coded out the long way in the
user.

PositionableStream>>back,current,previous,do:,at:,includes: - Added helpful
methods for stepping back and looking into the collection itself.

WriteStream>>insert:,removeNext: - Additional manipulation beside appending.

(The last two additions may not seam appropriate for streams if you look at a
stream like a pipe.  So I could be persuaded to move these to a new class.  But
the rest I believe are very appropriate for their specified classes.)

Cheers,
Anthony


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
From [email protected] Sun Jun 22 00:27:11 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 6855 invoked from network); 22 Jun 2003 00:27:11 -0000
Received: from iramx1.ira.uni-karlsruhe.de (141.3.10.80)
  by mail.theinternetone.net with SMTP; 22 Jun 2003 00:27:11 -0000
Received: from acb290c8.ipt.aol.com ([172.178.144.200]
	helo=i09nbmarcus.ira.uka.de)
	by iramx1.ira.uni-karlsruhe.de with asmtp (Exim 3.30 #10 (Debian))
	id 19TshJ-0004Ve-00; Sun, 22 Jun 2003 02:27:09 +0200
Received: from marcus by i09nbmarcus.ira.uka.de with local (Exim 3.33 #2
	(Debian))	id 19Tsi9-0000Nv-00; Sun, 22 Jun 2003 02:28:01 +0200
Date: Sun, 22 Jun 2003 02:28:01 +0200
From: Marcus Denker <[email protected]>
To: [email protected],<[email protected]>
Subject: Re: [Squeakfoundation]ContextCleanupPlus-ajh (was: Re: KCP & 3.6)
Message-ID: <[email protected]>
References: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.4.1i
X-BeenThere: [email protected]
X-Mailman-Version: 2.1
Precedence: list
Reply-To: Discussing the Squeak Foundation
	<[email protected]>
List-Id: Discussing the Squeak Foundation
 <squeakfoundation.lists.squeakfoundation.org>
List-Unsubscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=unsubscribe>
List-Archive: <http://lists.squeakfoundation.org/pipermail/squeakfoundation>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=subscribe>
X-List-Received-Date: Sun, 22 Jun 2003 00:27:11 -0000

On Sat, Jun 21, 2003 at 03:07:41PM -0700, Anthony Hannan wrote:
> 
> Of course, cleanup involves changes to existing classes.  If you're talking
> about the additional protocol I've added to general classes, below are the
> detailed explanations.  I think you will agree they a reasonable, and truly
> belong as class extensions rather than in user classes where they would be
> tedious and less reusable.  I would not be afraid to add these new protocols
> especially since they can't affect any existing code.  Note, many of the users
> are in ClosureCs and not in ContextCleanupPlus itself.
> 
I vote for adding this. My personal development image has this loaded
(last 3 Months) with no problems. 

   Marcus


-- 
Marcus Denker [email protected]  -- Squeak! http://squeak.de