From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,791530e499e6a7f9 X-Google-Attributes: gid103376,public From: Ted Dennison Subject: Re: ada writing guide Date: 2000/04/17 Message-ID: <8dfpj7$crs$1@nnrp1.deja.com>#1/1 X-Deja-AN: 612357346 References: <8d1rso$bir$2@bunyip.cc.uq.edu.au> <8d1vhj$hdr$1@nnrp1.deja.com> <8d2hig$7e6$1@nnrp1.deja.com> <38F5DF8C.1A01E5A4@utech.net> <8d4t07$o15$1@nnrp1.deja.com> <38F603FE.B0C3ED83@utech.net> <8d5dsc$c27$1@nnrp1.deja.com> <8d6hjn$j9p$1@clnews.edf.fr> <8d76vj$9jt$1@nnrp1.deja.com> <8d7uak$1d1$1@wanadoo.fr> <8dfd6q$uch$1@nnrp1.deja.com> <87em84vavt.fsf@deneb.cygnus.argh.org> X-Http-Proxy: 1.0 x21.deja.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Apr 17 19:44:43 2000 GMT X-MyDeja-Info: XMYDJUIDtedennison Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.7 [en] (WinNT; I) Date: 2000-04-17T00:00:00+00:00 List-Id: In article <87em84vavt.fsf@deneb.cygnus.argh.org>, Florian Weimer wrote: > Ted Dennison writes: > > > I do have one (minor) problem with the implementation, though. It > > looks like the exception file is read once at startup into an > > internal buffer. When someone adds an entry, it is their internal > > copy that is added to, then written to disk. If another user > > changed that file in the meantime, their changes are lost. This, > > combined with the advice for projects to keep one master file which > > everyone uses, could lead to a big mess. > > Put the file under version control. I'm amazed to see that there are > still projects with multiple developers which do not use it. ;) > We do of course. I thought there was about a %30 chance someone would bring this up. :-( That is the first thing I thought of as well. However, further thought will show you that it won't really solve the problem. It just gives us a recovery option from particularly bad losses, at the cost of a lot of overhead around any changes. To help you see, cosider the following scenario: Monday Fred opens up an emacs session. Tuesday, Joe opens up an emacs session and adds 3 capitalizations. Wednesday, Joe adds 3 more capitalizations Thursday, Joe adds 3 more capitalizations Friday, Fred adds 5 capitalizations (wiping out all of 6 Joe's) Monday, Joe adds 4 more capitalizations (wiping out Fred's 5) etc. With revision control, we have: Monday Fred opens up an emacs session. Tuesday, Joe opens up an emacs session, checks out the cap file, adds 3 capitalizations, and checks back in the cap file. Wednesday, Joe checks out the cap file, adds 3 more capitalizations, and checks back in the cap file. Thursday, Joe checks out the cap file, adds 3 more capitalizations, and checks back in the cap file. Friday, Fred checks out the cap file, adds 5 capitalizations, and checks back in the cap file. (wiping out all 6 of Joe's) Monday, Joe checks out the cap file, adds 4 more capitalizations, and checks back in the cap file (wiping out Fred's 5) etc. -- T.E.D. http://www.telepath.com/~dennison/Ted/TED.html Sent via Deja.com http://www.deja.com/ Before you buy.