X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 22 Nov 2007 12:14:31 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Announce: FlexDLL, flexible DLLs under Windows Message-ID: <20071122171431.GB29996@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4744E9AE DOT 664E0AF8 AT dessent DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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. My $.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. 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/