Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!tiamat!quintro!reb
From: reb@quintro.UUCP (Roger E. Benz)
Newsgroups: comp.sys.apollo
Subject: Re: DSEE Opinions
Message-ID: <349@quintro.UUCP>
Date: 5 Jun 89 16:13:10 GMT
References: <3860@hacgate.scg.hac.com> <11400011@uicsrd.csrd.uiuc.edu>
Reply-To: reb@quintro.UUCP (Roger E. Benz)
Organization: none
Lines: 31

In article <11400011@uicsrd.csrd.uiuc.edu> hoefling@uicsrd.csrd.uiuc.edu writes:
>
>If you want to use file names that contain UPPER CASE letters, DSEE is a 
>pain to use.  It is case-insensitive and converts any upper case letters it
>sees to lower case.  For a module name like "p_EXTERNAL.c", you have to write
>it as "p_:e:x:t:e:r:n:a:l.c", which is pretty painful.  Also, when BUILDing
>your system, it simply can't find files that you have checked-out ("reserved" 
>in DSEE) in your working directory if any part of the file name or the
>path contains even one upper case letter.
>

Release 3.2 and 3.3 of DSEE is case-sensitive.  3.2 is for SR9.7 nodes and
3.3 is for SR10 nodes.

Also, I have been using DSEE for three years and I really like it.  Its
best features are:  Remote building using NCS, -target option for building
different versions of the software for different platforms, multi-user
and multi-node support DSEE can be ran from either a node or a terminal
connected to a serial port.

As far as task lists and monitors we don't use them (they could be useful,
however).

One thing I have learned is that for just one person on a project DSEE is
a little more cumborsome than using 'make'.  But if two or more people are
involved DSEE is nice.

-- 
Roger E. Benz		   Phone = (217) 223-3211
Quintron Corporation	   Quincy, Il
UUCP: tiamat!quintro!reb@uunet or quintro!reb@lll-winken