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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,1354ef03380fbbb
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-05-13 06:35:25 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <Stephe.Leake@nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: Ann: TeXCAD 4.0 (-\epsilon)
Date: 13 May 2003 09:32:50 -0400
Organization: NASA Goddard Space Flight Center (skates.gsfc.nasa.gov)
Message-ID: <uvfwfgef1.fsf@nasa.gov>
References: <mailman.30.1052521816.9816.comp.lang.ada@ada.eu.org>
 <u1xz49na6.fsf@nasa.gov> <17cd177c.0305130204.6f187afd@posting.google.com>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 1052833700 27174 128.183.235.92 (13 May 2003
 13:48:20 GMT)
X-Complaints-To: usenet@news.gsfc.nasa.gov
NNTP-Posting-Date: 13 May 2003 13:48:20 GMT
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Xref: archiver1.google.com comp.lang.ada:37275
Date: 2003-05-13T13:48:20+00:00
List-Id: <comp.lang.ada>

gautier_niouzes@hotmail.com (Gautier) writes:

> Stephen Leake:
> 
> > Hmm. I downloaded it, unzipped TeXCAD.exe to a place in my PATH, and
> > ran texcad. The first time, it gave an error box, something about the
> > registry not finding a file. As usual for MS error messages, it didn't
> > say what file. But then, when I tried it again, to reproduce the error
> > message, I didn't get the error message.
> 
> The error is fixed. It was indeed an unavoidable one... Thank you for
> mentioning it.

Hmm. "unavoidable" errors that are now fixed; that's a conundrum :).

> > I _strongly_ urge you to not use the Windows Registry for
> > _anything_! It is a royal pain, hard to test, hard to debug.
> 
> If you have a better way, I am all ears!

Well, I need to know what you are using the registry for; I have not
yet downloaded the sources, nor did I peek into the registry to see
what you had done to it.

> > But the worst thing is that the user cannot change settings on a
> > per-process basis; the registry is strictly per-user.
> 
> But how do Install Shield & Co clear the options for all users when
> uninstalling ?

I don't see how that is relevant to my point. I assume they have a
list of registry keys they installed, and they simply delete them.

Which is one problem with the registry approach; if I manage to
install version 3.2 and 3.3 of something, and then uninstall 3.3, 3.2
probably doesn't work any more.

-- 
-- Stephe