X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: From: Sravan Bhamidipati Date: Wed, 29 Jun 2011 08:06:41 +0530 Message-ID: Subject: Re: Programming Anti-patterns in Shell and Perl Scripts To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 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 28/06/2011 3:21 PM, Ryan Johnson wrote: > I don't use bash-completion myself, but my understanding is > that it can be very slow, if for no other reason than fork() is > slow in cygwin. If your de-anti-pattern transformation causes > fewer calls to fork() -- and the above expr example suggests > it does -- it could be very worthwhile. That's the basic underlying principle to start with, Ryan. That in general: Accessing memory << Calling a function << Forking a process. > Implementation-wise, you probably want to start here: > http://www.cygwin.com/contrib.html You mean directly making those changes? I've never done that before, so I was hoping to catch the attention of a few of the package owners/contributors and give/take their help. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple