Kenneth Bandes wrote:
> Granted, if a DLL really is part of the operating system and ought
> to be shared, it should go into System32. But then, should parts
> of the operating system really be distributed with each application
> you install? This is a weird custom that only occurs with Windows -
> in other operating systems, no-one would dream of replacing parts
> of the OS when you install their apps.
Well, that depends on how you define "Operating System". On one
extreme, you have Linux, where the kernel is the OS. Everything else is
an add-on. Even the filesystem is considered value-added (At last check
there were something a half-dozen different file systems to choose from,
including minix, ext, ext2 and sysv).
At the oposite end of the spectrum is Windows, which some would have you
believe includes not only the kernel, file system, windowing system and
command shell, but also end-user applications such as web browsers.
But back to the original topic, if a DLL is used to encapsule
functionality specific to an application, than I agree it should be
stored in the same location as the executable. Otherwise, it makes
sense to store them in central location, whether that be
C:\Winnt\System32 or /usr/lib. In the end, it should be the decision of
the individual installing the software, not the software author (after
all, it's his/her system).
Regards,
Ian
--
99 little bugs in the code, 99 bugs in the code.
Fix one bug, compile again, 100 little bugs in the code.
100 little bugs in the code, 100 bugs in the code.
Fix one bug, compile again, 101 little bugs in the code...
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
