From:	"A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Long filename problem
Date:	Sun, 15 Jun 1997 22:38:43 -0400
Organization:	Cornell University http://www.cornell.edu
Lines:	36
Sender:	asu1 AT cornell DOT edu (Verified)
Message-ID:	<33A4A733.9E3@cornell.edu>
References:	<33A4C1C8 DOT 2FB9 AT tiac DOT net>
Reply-To:	asu1 AT cornell DOT edu
NNTP-Posting-Host:	cu-dialup-0019.cit.cornell.edu
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Claude Sassine wrote:
> 
> In trying to create a file from with a C program with filename longer
> than 8 characters, two questions came about. One, can the size the
> filename be changed by adjusting a header file variable? The stdio.h
> file defines the FILENAME_MAX=260, but the only 8 characters are
> permited. Is there some other variable that can changed to accomplish
> this?

i am not sure i understand what you are saying correctly, but if you
think you can get long file names on a system that does not support them
(such as dos 6.22/win 3.1x) by adjusting a macro definition, you are
mistaken. consult the faq regarding details on lfn.
 
> Secondly, the information in a open file does not seem to be written
> onto the hard drive until after the program ends. This was done using
> the fopen and fclose commands. The header files seem to offer more
> processing than I am aware of, but time has not allowed me the chance 
> to read the information at the DJGPP website. Can the data onto be 
> stored onto hard drive, intermittently, as the program continues 
> processing?
 
you need to use fflush to commit buffers to disk. do read the
documentation, the C and C++ faqs and consider getting an introductory C
book.
-- 
   Sinan
 
*******************************************************************
 A. Sinan Unur                                WWWWWW
                                              |--O+O
 mailto:sinan DOT unur AT cornell DOT edu                C   ^ 
 http://www.people.cornell.edu/pages/asu1/     \  ~/ 

Unsolicited e-mail is _not_ welcome, and will be billed for.
*******************************************************************

- Raw text -