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: Thu, 28 Feb 2002 15:01:51 -0500 From: Jason Tishler Subject: Re: setup.exe rebase patch In-reply-to: <20020228184644.GB1980@hp.com> To: Robert Collins , Cygwin-Apps Mail-followup-to: Robert Collins , Cygwin-Apps Message-id: <20020228200151.GA1392@hp.com> 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: <20020228184644 DOT GB1980 AT hp DOT com> Rob, On Thu, Feb 28, 2002 at 01:46:44PM -0500, Jason Tishler wrote: > > The Memento class is designed to provide a solution to both issues. > > Thanks for pointing me to the Memento pattern. I will investigate it > and try to come up with a better solution. I just read the Memento chapter in the Gang of Four book. I don't see how this pattern will help in this case because the Memento object is suppose to be opaque. The Memento pattern's canonical use is to assist with undo operations (i.e., restore state) without breaking encapsulation. I don't see how to twist this pattern for use by a general persistence mechanism. Jason