Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-Id: <4.3.1.2.20010914133411.0305aee8@pop.ma.ultranet.com> X-Sender: lhall@pop.ma.ultranet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 14 Sep 2001 13:37:09 -0400 To: "Brian J. Ackermann" , From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Convince the Supervisor Time... In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 12:47 PM 9/14/2001, Brian J. Ackermann wrote: >Hello, > >Myself and another co-worker have been interested in cygwin for quite some >time now, and we've finally managed to convince our management to consider >adding cygwin to our tool-set. > >Basically, our situation would be the integration of various Visual Studio >applications with perl applications and shell scripts. > >Presently we are just using VS and batch files. > >Our questions mostly are pointed at other developers/integrators who are >doing similar things. > >Is cygwin/[bash , perl] up to the task of full scale production. Are there >any memory leaks or other things that would prevent us from going where we >desire? Like all software, Cygwin is in a state of constant change and improvement. Given the very general hint as to your intended use of Cygwin, it should work for you just fine. I'd suggest installing Cygwin and setting up a few tests that mimic how you plan to use it. This should tell you most directly whether you'll have any major problems with your intended use. Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/