From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8acd4291c317f897 X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,8acd4291c317f897 X-Google-Attributes: gid109fba,public From: Hyman Rosen Subject: Re: Safety of the Booch Ada 95 Components Date: 1999/12/13 Message-ID: #1/1 X-Deja-AN: 560206889 Sender: hymie@calumny.jyacc.com References: <1e2lds4.7trgj21rgj9i0N%herwin@gmu.edu> <38512921_3@news1.prserv.net> <3851c7b9_4@news1.prserv.net> X-Complaints-To: abuse@panix.com X-Trace: news.panix.com 945114709 9822 209.49.126.226 (13 Dec 1999 19:51:49 GMT) Organization: PANIX Public Access Internet and UNIX, NYC NNTP-Posting-Date: 13 Dec 1999 19:51:49 GMT Newsgroups: comp.lang.ada,comp.lang.c++ Date: 1999-12-13T19:51:49+00:00 List-Id: "Matthew Heaney" writes: > We make this assumption per the "design-by-contract" model. If you give > me an assignment operator that doesn't work, and it raises an exception > (say), then yes, that would leave the target object in an inconsistent > state. > > If you don't like that, then don't give me a broken assignment operator. Why is an assignment operator that raises an exception broken?