Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2042
Path:	news-dnh.mv.net!mv!news.sprintlink.net!usenet.kornet.nm.kr!ames!lll-winken.llnl.gov!fnnews.fnal.gov!stc06.ctd.ornl.gov!cs.utk.edu!not-for-mail
From:	mwilliam AT cs DOT utk DOT edu (Myles Barrett Williams)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Changing CHDIR and MKDIR semantics
Date:	14 Sep 1995 16:46:11 -0400
Organization:	CS Department, University of Tennessee, Knoxville
Lines:	18
References:	<DEuxCz DOT IsE AT jade DOT mv DOT net>
Nntp-Posting-Host:	hydra4b.cs.utk.edu
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <DEuxCz DOT IsE AT jade DOT mv DOT net> Marc Singer <nbn.nbn.com!sapien!elf> writes:
>If I'm on c: and I do the above command, I am still on c:, but this
>behavior is not expected by the UN*X program.  I had to write a new
>
>So, the questions is whether or not we want to support a UN*X
>compatible behavior in chdir.  I suspect something similar happens in

I say change it for Unix compatibility.  If a path starts with
a slash, chdir should check whether the first directory is a letter
followed by a colon.  If so, it switches drives, else it changes
relative to the current drive.

If we put the above version of chdir under an #ifdef _POSIX_SOURCE
directive, and the DOS style chdir under #else, that would increase
portability for Unix programs while leaving DOS-based programs
alone.

Myles Williams		"When you see me again, it won't be me."

- Raw text -