public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Why is Cygwin1.dll monolithic?
@ 2006-06-10 12:04 Václav Haisman
  2006-06-10 16:52 ` Erich Dollansky
  2006-06-10 17:51 ` Christopher Faylor
  0 siblings, 2 replies; 3+ messages in thread
From: Václav Haisman @ 2006-06-10 12:04 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

Today I woke up and one of the first things that came on my mind was
this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

--
Vaclav Haisman

PS: I am not trying to suggest anything or to troll, I am merely curious.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 544 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Why is Cygwin1.dll monolithic?
  2006-06-10 12:04 Why is Cygwin1.dll monolithic? Václav Haisman
@ 2006-06-10 16:52 ` Erich Dollansky
  2006-06-10 17:51 ` Christopher Faylor
  1 sibling, 0 replies; 3+ messages in thread
From: Erich Dollansky @ 2006-06-10 16:52 UTC (permalink / raw)
  To: cygwin

Hi,

Václav Haisman wrote:
> Today I woke up and one of the first things that came on my mind was
> this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

isn't it just the API?

So why should there be a 'kernel'?

Erich


--
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Why is Cygwin1.dll monolithic?
  2006-06-10 12:04 Why is Cygwin1.dll monolithic? Václav Haisman
  2006-06-10 16:52 ` Erich Dollansky
@ 2006-06-10 17:51 ` Christopher Faylor
  1 sibling, 0 replies; 3+ messages in thread
From: Christopher Faylor @ 2006-06-10 17:51 UTC (permalink / raw)
  To: cygwin

On Sat, Jun 10, 2006 at 12:28:00PM +0200, V??clav Haisman wrote:
>Today I woke up and one of the first things that came on my mind was
>this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

Maybe you should outline the benefits of such a plan since I can only
see drawbacks.  Both DLLs would have to be loaded by every application
anyway.  That means two separate directory lookups.  And, the "separate
C library" would suffer from dll load-time issues with accessing data
and functions, i.e., it would be slower than the current way of doing
things.  And, then, there would be the "It says cyglibc.dll not found.
Why it not there?" issues that are sure to crop up.

So, other than the esoteric issue of isolating things into separate
regions for maintenance sake, I don't see any end-user benefits.

cgf

--
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-06-10 16:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-10 12:04 Why is Cygwin1.dll monolithic? Václav Haisman
2006-06-10 16:52 ` Erich Dollansky
2006-06-10 17:51 ` Christopher Faylor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).