delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/06/09/12:31:15

From: mapson AT mapson DOT com (Mapson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Changing filenames with DJGPP
Date: Tue, 09 Jun 1998 16:01:46 GMT
Organization: Yale University
Lines: 27
Message-ID: <357d5a3c.9190552@news.cis.yale.edu>
References: <19980609000834 DOT AAC6349 AT ppp100 DOT cartsys DOT com>
NNTP-Posting-Host: logan.eng.yale.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Mon, 8 Jun 1998 17:08:39 -0700, Nate Eldredge <nate AT cartsys DOT com>
wrote:

<...>

>If you set LFN=Y in the environment, all library functions will
>automagically understand long file names under Windows 95. This includes
>`rename', which appears to be what you want.

Actually, that was helpful, even though i guess I didn't phrase my
question well. I am enjoying compiling some long-named MSVC++ console
code with DJGPP now that I know this detail- thanks.

About my real issue: rename was indeed a good function call for what I
was looking for, and the other key ones seem to be (after much random
libc wanderings):
findfirst, findnext, and the rather worrisome "__file_exists." I am
relying pretty heavily on this __file_exists at the moment, and it
certainly looks good, and is easy, small and quick... one question,
though: can it reliably be expected to return "exists!" code also when
it finds a directory? So far, I'd say yes, from my experimentation.
But I definitely want to know for sure, and the docs don't really say
much about it. Also, if someone has any good reasons I shouldn't use
__file_exists, please let me know- I already know it isn't
particularly ANSI nor portable, but beside that...

Thanks!

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019