Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Brian J. Ackermann" <brianj774 AT gmx DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	Convince the Supervisor Time...
Date:	Fri, 14 Sep 2001 11:47:33 -0500
Message-ID:	<DHEFJJMMGOIPNHNLBIGNCEMKCEAA.brianj774@gmx.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

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?

Thanks for your consideration,

Brian J. Ackermann
API


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

- Raw text -