Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!dwp
From: dwp@willett.pgh.pa.us (Doug Philips)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Thompson Toolkit (was Re: Where can I get MKS toolkit?)
Message-ID: <2894.UUL1.3#5129@willett.pgh.pa.us>
Date: 17 Jun 91 14:45:10 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 26

In article <72771@microsoft.UUCP>,
	steveha@microsoft.UUCP (Steve HASTINGS) writes:
+                IMHO, MKS is unusable because they insist on treating
+"c:foo" as identical to "c:/foo"; they claim this is more UNIX compatible
+and therefore desirable.  I say that if I had meant "c:/" I would have
+typed "c:/" instead of "c:" and it is a pain to use MKS when you work with
+networks and can have long paths on a half dozen drives or more.

*I guess it just depends on what you are used to.*  I for one never got
used to a device dependant current directory, so I always used full path
names anyway.  I find that it is useful to define shell variables for
commonly accessed directories _and_ files, and as I use two character
names for the commonest among them, that is only one character more than
the supposed win of "c:".  As for "unix compatible", it certainly seems
to me that when you name the device you are naming the root directory of
that device...

+Technical support from Thompson Automation has been outstanding.  The
+author of the software, Pat Thompson, often answers questions.

I can't say anything about the Tech. Support at MKS because I've never
needed to use it.

-Doug
---
Preferred:  dwp@willett.pgh.pa.us	Ok:  {pitt,sei,uunet}!willett!dwp