Re: ada writing guide

[Ted Dennison <dennison@telepath.com>]

In article <874s8yeg81.fsf@deneb.cygnus.argh.org>,
  Florian Weimer <fw-usenet@deneb.cygnus.argh.org> wrote:
> Ted Dennison <dennison@telepath.com> writes:
>
> > No warnings are given, no backups are made. The old version is
> > over-written. Even for those who know the danger, this would be easy
to
> > accidentally do.
>
> This can't happen with systems like CVS where each user works on his
> private copy of the source files.  The master files are often not
> directly accessible.  Problem solved. ;)

Hmm. I use CVS at home, but I guess that's not multiuser (yet, perhaps
It'll be that way when my kids are older :-)  ).

I'm still not convinced CVS wouldn't have the problem too. But at least
the process give you one hint. I see it working this way.

  User A does a "cvs checkout" of the repository
  User B does a "cvs checkout" of the repository
  User A starts up emacs (which reads the exception file into memory).
  User B starts up emacs (which reads the exception file into memory).
  User A hits Ctrl-C Ctrl-Y
  User A does a "cvs commit" on the exception file
  User B finds out there were changes, and does a "cvs update"
  User B hits Ctrl-C Ctrl-Y (unknowingly wiping out user A's changes)
  User B does a "cvs commit"

At least this way, there is a manual updating step in there, where the
wise user could say, "I'd better bring my emacs up to date, just to be
safe." But it'd still be awfully easy to forget, or overlook a running
session somewhere.

--
T.E.D.

http://www.telepath.com/~dennison/Ted/TED.html


Sent via Deja.com http://www.deja.com/
Before you buy.