From dougo@ccs.neu.edu Wed Dec 5 13:40:42 2001 X-UIDL: 4f5996e4d4901eea348a06456de57764 Return-Path: Received: from vega.ccs.neu.edu (vega.ccs.neu.edu [129.10.116.206]) by amber.ccs.neu.edu (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id fB5IecH12766; Wed, 5 Dec 2001 13:40:38 -0500 (EST) Received: by vega.ccs.neu.edu (Postfix, from userid 6068) id 752A09C63; Wed, 5 Dec 2001 13:40:35 -0500 (EST) From: Doug Orleans Message-ID: <15374.27170.744534.145317@vega.ccs.neu.edu> Date: Wed, 5 Dec 2001 13:40:34 -0500 (EST) To: Karl Lieberherr Cc: skotthe@ccs.neu.edu, edwards@intranet.com, johan@ccs.neu.edu, john_j_sung@yahoo.com, neerajsangal@mediaone.net, robby@ccs.neu.edu, wupc@ccs.neu.edu Subject: Re: contracts and AOP In-Reply-To: <200112051636.fB5Ga8h22013@gomeisa.ccs.neu.edu> References: <200112051636.fB5Ga8h22013@gomeisa.ccs.neu.edu> X-Mailer: VM 6.72 under 21.1 (patch 3) "Acadia" XEmacs Lucid X-Face: (4D-osoq?}7M3\EgvbWKo Doug proclaimed the following guidelines: > > Adding an aspect should not change (invalidate?) > pre- and post- conditions of existing code. > > Adding an aspect should lead to a behavioral subtype. I think "proposed" is a better word than "proclaimed". Or more like, "hypothesized". I think Theo is right, it depends on the aspect. Perhaps that would be a way to categorize aspects: those that preserve contracts and those that invalidate contracts, without making a value judgement on the latter category. --Doug