Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 21 Nov 2003 11:25:44 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: For masochists: the leap o faith Message-ID: <20031121102544.GA9027@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031114220708 DOT GA26100 AT redhat DOT com> <3FB55BCE DOT 8030304 AT cygwin DOT com> <20031115044347 DOT GA29583 AT redhat DOT com> <1068883645 DOT 1109 DOT 122 DOT camel AT localhost> <20031115164534 DOT GB3039 AT redhat DOT com> <20031115165229 DOT GA3296 AT redhat DOT com> <1068930608 DOT 1109 DOT 172 DOT camel AT localhost> <20031117105635 DOT GD18706 AT cygbert DOT vinschen DOT de> <1069361916 DOT 1117 DOT 46 DOT camel AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1069361916.1117.46.camel@localhost> User-Agent: Mutt/1.4.1i On Fri, Nov 21, 2003 at 07:58:36AM +1100, Robert Collins wrote: > On Mon, 2003-11-17 at 21:56, Corinna Vinschen wrote: > > On Sun, Nov 16, 2003 at 08:10:08AM +1100, Robert Collins wrote: > > > We have two choices (no particular order of preference): > > > a) make MAX_PATH and posix friends the maximum length path cygwin will > > > accept/return. Return ENAMETOOLONG on path calls on win9x, or winnt > > > FAT[32] calls. Update pathconf to return appropriate values. > > > b) blow away MAX_PATH and MAXPATHLEN so that programs using cygwin > > > fallback to pathconf, or 'good enough for me' static arrays. Update > > > pathconf to return appropriate values. > > > > Well, I guess you meant PATH_MAX here. > > Yes, of course. > > > I would prefer to change PATH_MAX and MAXPATHLEN to an arbitrary big > > value as, e. g. the same as on Linux, 4096, or even the biggest possible > > plus one: 32768. The latter is probably the better value. So my choice > > is a) > > Ok. What should we set CYG_MAX_PATH to initially then? I think we should > start at 4K, until we've seen whether there are any stack size issues. I think we should get rid of static buffers in most cases. Some of them might be kept in place, returning to MAX_PATH, the others should use another technique, like alloca. As I see it, CYG_MAX_PATH should be just a temporary measure. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/