Re: Windows Installer for CLISP

[Arseny S. <am...@ic...>]

Hi, Elliott, thanks for the installer!

> The way the installer is set up right now, it just pulls in the files
> with one massive file glob, so the installer doesn't actually know the
> difference between the two linking sets. It just links all the
> shortcuts and file associations it creates to the chosen linking set.
> I did this firstly because it was just easier, and secondly because
> that's what you get when you install manually from the zip file and
> run install.bat. It wouldn't theoretically be that difficult to
> change... I just haven't tried yet.

>> I wonder if your installer should allow both the base and
>> full linking sets to be installed side-by-side if the user wants,
>> rather than only allowing one or the other to be selected?

I seem to remember why two different linking sets are required.
There are some system functions in the full linking set what are exist
not on all systems. I.e. it were absent on windows 98. I even wrote
some code to dynamically load some of them and if they're absent
report runtime error at the time the function is invoked, so lisp.exe
can be loaded. I wonder if the need in the two linking sets still
present. So, if it is the only reason to have two lisp versions, you
can leave the installer as is in this regard, because set the user
working with is related to his operating system. But I see that now
those functions are in both linking sets and the only difference I
could find is the presence of PCRE package in the full one.

Starting shortcut should be "Gnu Clisp x.xx", as it is for another
programs, not "Run GNU Clisp".

I could not find clisp record in the "Add/Remove programs" in the
Control Panel. Probably the record should be placed there.

Finally, novice user should be told somehow about the difference
between the two linking sets. Actually, me too.

-- 
Arseny