X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: ActiveState Perl and Cygwin How To Date: Mon, 8 Feb 2010 15:42:11 +0000 (UTC) Lines: 32 Message-ID: References: <1ef5a52f1002080454r6898f8b8hacd34335d92709bf AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Csaba Raduly gmail.com> writes: > > I have been using Cygwin for quite some time now on Windows XP. I use > > Perl extensively and the scripts I use/create are fairly portable. > > I want to use ActiveState Perl as I can install many modules from CPAN > > that give me trouble in Cygwin using cpan install ... Ultimately, it makes more sense to use Cygwin's perl with cygwin, rather than a third-party perl that doesn't understand cygwin. > P.S. Can somebody explain what ${1+"$@"} does and why it's used > instead of just $@ ? > I hate doing cargo cult programming. http://www.gnu.org/software/autoconf/manual/autoconf.html#Shell-Substitutions which documents how use of ${1+"$@"} works around bugs in older zsh and ksh. Actually, modern ksh apparently still has a different bug, which it does not work around: http://lists.gnu.org/archive/html/automake-patches/2010-02/msg00005.html so patches to the autoconf manual are welcome. But this is starting to stray (WAY) off-topic for cygwin. -- Eric Blake -- 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