X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Subject:	Re: Announce: FlexDLL, flexible DLLs under Windows
In-Reply-To:	<20071122171431.GB29996@ednor.casa.cgf.cx>
To:	cygwin AT cygwin DOT com
Date:	Thu, 22 Nov 2007 16:16:31 -0500 (EST)
X-Mailer:	ELM [version 2.4ME+ PL124 (25)]
MIME-Version:	1.0
Message-Id:	<E1IvJPT-00043V-AO@owl.gateway.2wire.net>
From:	Robert Kiesling <kiesling AT earthlink DOT net>
X-ELNK-Trace:	0b901cbc512a9d8594f5150ab1c16ac01a238acc8405a5b0ddd12836a75c5ef9ea4cd2ba8a088fbb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> On Thu, Nov 22, 2007 at 04:15:50AM -0500, Robert Kiesling wrote:
> >ISTM it would be easier to add event notifiers to the shell or the
> >app, although the implementation of that would almost certainly require 
> >a code fork.  And the memory management and the practice of loading Windows
> >apps with Unix is much better documented.  AND although Cygwin is limited by 
> >its use of static libraries in that regard, the task would not be impossible.
> >
> >Just my 0.02.
> 
> I can't grok most of the above.  Cygwin doesn't rely on a
> shell, adding "event notifiers" doesn't make a lot of sense in this
> context, and the mention of static libraries doesn't really seem
> pertinent to a disscussion of shared library loading.

The scenario is normal and expected - program that uses data for
another program and its libraries to finish before another program can
read the data written to disk, loaded and swapped in its memory and
then make use of the data.  The mechanisms of this scenario vary
between operating system and version.  Unfortunately, Cygwin apps do
rely on shells, or in the case of services, the exec () and similar
system calls that load the apps and libraries.  ISTM the previous
description obfuscates and in fact complicates the process.  The APIs
to accomplish those tasks already exist.  Anybody that wants to accomplish
the tasks has only to look them up for themselves.

-- 
Ctalk Home Page: http://ctalk-lang.sourceforge.net


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

- Raw text -