Common Lisp Development on Windows NT 4.0

[LarryA.Taylorltaylor at wisdomcorp.com]

We're a startup development company, a spin-off of Carnegie Mellon Univ.
here in Pittsburgh. Our product is in Allegro Common Lisp, and our 
development and delivery platforms are Windows NT 4.0.

I downloaded the demo.  From watching it work, it seems to assume connection
to the internet.  This is good. Is it important -- even relevant --
that the client and server be at the same site for Perforce?

Our company's requirements for configuration management.

- - The ability to have more than one person edit the same (source) file.
   (I believe this is a gimme.  How well does it work in practice?)
- - Good automatic merge support
- - Branching mechanisms. (Again, I observe the branching capability in
  the menus.  Does Perforce do this well?)
- - Able to run on NT (check) and with CommonLisp (can anybody help here?)
- - Ability to do source control access different development sites? (We
  need to sync with friends in Europe)

Less important

- - Ability to give it (a change set, I think) your own version numbers, or
  even names assigned to particular versions at the whole system level
  (I suppose the ability to ask, "was this line in the March Beta for 
   Madrid?")
- - ability to add and delete files from a configuration (seems so)
- - ability to add and delete directories from a configuration?
- - GUI interface rather than command line (check)
- - doesn't need unix in order to work (check)

The only problem I saw in my demo:

You don't like blanks in names of files or folders. Thousands of Mac
users died in the war for your freedom to have blanks in file names.

LAT
Larry A. Taylor, Ph.D. Wisdom Technologies
http://www.wisdomcorp.com/