Xref: news2.mv.net comp.lang.c:81284 comp.lang.c++:102867 comp.os.msdos.djgpp:7788
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.lang.c,comp.lang.c++,comp.os.msdos.djgpp
Subject: Re: fopen problem.
Date: Fri, 23 Aug 1996 09:28:24 +0200
Organization: NetVision LTD.
Lines: 12
Message-ID: <Pine.SUN.3.91.960823092519.4631K-100000@is>
References: <4v1gkv$kld AT lion DOT cs DOT latrobe DOT edu DOT au> <3219B4F3 DOT 2A41 AT iti-oh DOT com> <840644787snz AT genesis DOT demon DOT co DOT uk> <321BB9BF DOT 5A68 AT cs DOT com> <danpop DOT 840714366 AT news DOT cern DOT ch> <321B925B DOT 2178 AT idir DOT net>
NNTP-Posting-Host: is.elta.co.il
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <321B925B.2178@idir.net>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp


On Wed, 21 Aug 1996, Jason von Nieda wrote:

> If it bothers you so very much, get a DOS programming reference
> or Ralf Browns Int list and use the undoc'ed DOS int to change it
> to a forward slash.

I think that undocumented interrupt doesn't work anymore, beginning with
DOS 5.0.  However, DOS itself doesn't care at all to get forward slashes; 
it's only programs which come with DOS (like COMMAND.COM) that don't treat 
forward slashes as directory separators.  So if you only use Unix-style 
pathnames in your programs, you don't have to bother about this issue.