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:[EMAIL PROTECTED] 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/
