X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 31 Oct 2008 10:00:50 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: canonicalize_file_name In-Reply-To: <490B0243.2040504@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <001b01c93a65$97134460$4001a8c0@mycomputer> <49099F53.9060105@byu.net> <20081030121050.GL6478@calimero.vinschen.de> <007f01c93abc$68806f40$4001a8c0@mycomputer> <20081031082454.GB12818@calimero.vinschen.de> <20081031111722.GA14239@calimero.vinschen.de> <490B0243.2040504@byu.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Oct 31, 2008 at 9:04 AM, Eric Blake wrote: > POSIX 200x (which is on track to be approved later this year) has modified > the requirements on realpath() that NULL be a universally accepted > argument. Oh, good. > Not all vendors comply with this yet, but at some point, it > will no longer be a GNU extension, but a POSIX-mandated requirement that > realpath() be able to malloc its result. This is part of the overall > paradigm change in POSIX 200x that recognizes that it is legal to have > paths longer than PATH_MAX I haven't tested it, but IIRC, GNU's version doesn't currently support such paths, either. It allocates the buffer for you if you pass in NULL, but it still only allocates PATH_MAX bytes. Thanks for the info. Anything to improve that interaction is a welcome change. The idea of a "maximum path length" is demonstrably bogus, while string functions that take a destination buffer but no size parameter are just plain dangerous. -- Mark J. Reed -- 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/