Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 6 Oct 2004 14:35:09 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] cygrunsrv --recovery <action>
Message-ID: <20041006123509.GH6702@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20041006120558 DOT GA5605 AT cygbert DOT vinschen DOT de> <NUTMEG5VxvCFvPjSk0i000002b2 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NUTMEG5VxvCFvPjSk0i000002b2@NUTMEG.CAM.ARTIMI.COM>
User-Agent: Mutt/1.4.2i

On Oct  6 13:16, Dave Korn wrote:
>   Well, of course, if you're using the API routine rather than going behind
> its back, then when M$ change the registry format, the code will continue to
> work.......  that is the whole idea for an API.
> [...]
>   See, I think that the best generic solution to this situation is to write
> code that dynamically links to ChangeServiceConfig2 if available, and falls
> back to writing hard-formatted registry keys/values only if that is not
> available.  That's both backwardly *and* forwardly compatible, as opposed to
> the current solution, which is fragile.  

Sure, that's fine (and done that way in the Cygwin DLL itself).
So now just http://cygwin.com/acronyms/#SHTDI , right? ;-)

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/