Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Wed, 3 Jul 2002 13:40:04 +0300 From: Ville Herva To: cygwin@cygwin.com Subject: Re: Accessing filenames with different charsets Message-ID: <20020703104004.GK9092@niksula.cs.hut.fi> References: <20020701085851.GD9092@niksula.cs.hut.fi> <20020702213825.GF9092@niksula.cs.hut.fi> <01f801c22212$7d0cecf0$0100a8c0@advent02> <20020703093837.GI9092@niksula.cs.hut.fi> <004e01c22278$346ec610$0100a8c0@advent02> <20020703101822.GJ9092@niksula.cs.hut.fi> <008c01c2227c$a10a96b0$0100a8c0@advent02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <008c01c2227c$a10a96b0$0100a8c0@advent02> User-Agent: Mutt/1.3.25i On Wed, Jul 03, 2002 at 11:30:19AM +0100, you [Chris January] wrote: > Since most programs internally allocate a buffer of size MAX_PATH or > PATH_MAX, they won't have enough room to store the full filename. True. > Tt would certainly be possible to support this if a system call was made > with a long filename, Problem here is is that you can't get the long filename from readdir() and friends if the d_name field is limited. So I imagine things like tar and rsync wouldn't work anyway. > but that would mean replacing all statically allocated path buffers (e.g. > char buf[MAX_PATH]) with alloca (e.g. char > *buf = alloca (strlen(inbuf) + margin)) which is more than trivial. Yes, sounds quite tedious. In this case one could imagine using the 8.3 name... -- v -- v@iki.fi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/