Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 11 May 2011 07:48:41 -0500
Message-ID: <4DCA85A9.4806@mindspring.com>
Date: Wed, 11 May 2011 08:48:41 -0400
From: pete <pfiland@mindspring.com>
Reply-To: pfiland@mindspring.com
Organization: PF
X-Mailer: Mozilla 3.04Gold (WinNT; I)
MIME-Version: 1.0
Newsgroups: comp.unix.programmer,comp.lang.c
Subject: Re: Avoiding recursive stack overflow in C on Unix/Linux?
References: <iptr5l$tkb$1@speranza.aioe.org> <ce8a87e8-fffa-4287-84ee-271f0766c304@24g2000yqk.googlegroups.com> <e154ec52-5ee3-41de-ad60-37f604e594f6@b19g2000yqg.googlegroups.com> <iq8j7v$28f$1@speranza.aioe.org> <cdc2bce7-4168-4bad-92b7-fdaa78e556e9@b19g2000yqg.googlegroups.com> <rubrum-F1F569.15051809052011@news.albasani.net> <2f33e674-b127-4c35-89b5-dcbf564f3aab@h36g2000pro.googlegroups.com> <yw1x7h9zebob.fsf@unicorn.mansr.com> <92rabuF51pU6@mid.individual.net> <yw1x39kneagb.fsf@unicorn.mansr.com> <87zkmvhyqm.fsf@temporary-address.org.uk> <rubrum-624DB0.12245510052011@news.albasani.net> <dc8b6c27-f53b-45a7-9804-4c65c10f40be@j13g2000pro.googlegroups.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 12
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 4.154.223.42
X-Trace: sv3-nvjGcd40Aqh8zzs6AiEYuQFOoIMDCa7QCGAY88YWreZV7ZQVH0OsIxdaGWrYCfseZIWMxTUin7WwcLx!WEAHfAXWQy/pRLv90x7shcYOb8I92T1ePhcrGk8aVrTZwmRlOMim99p+vW/wVUvmstkLEX99VqW4!9OubYH4G+A==
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1869
Xref: x330-a1.tempe.blueboxinc.net comp.unix.programmer:526 comp.lang.c:3746

ImpalerCore wrote:

>   ssize_t l

>        * l - low boundary of region to search

>       l = 0;

I don't like 'l' as a name for a variable.

-- 
pete