Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 05 Mar 2002 08:07:40 -0500 From: Jason Tishler Subject: Re: setup.exe rebase patch In-reply-to: To: Robert Collins Cc: Cygwin-Apps Mail-followup-to: Robert Collins , Cygwin-Apps Message-id: <20020305130740.GF1696@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: Rob, On Sun, Mar 03, 2002 at 06:20:33AM +1100, Robert Collins wrote: > Well if you can clarify what aspect is cheating, I'm happy to discuss > factoring approaches. Sorry for being vague and for being flippant too. By "cheating," I was specifically referring to violating a basic premise of the Memento pattern -- which is the state is opaque. As you have already mentioned, either the object must persist itself or something external must perform this operation. The Memento pattern seems to be a reasonable factoring approach that minimizes the breaking of encapsulation. I will either use this approach or have my list/map class persist itself to/from your io_stream class. Thanks, Jason