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 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/20 Message-ID: <38FF4D28.8F946BDA@telepath.com>#1/1 X-Deja-AN: 613681895 Content-Transfer-Encoding: 7bit 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> <8dfpj7$crs$1@nnrp1.deja.com> <38FF1D6B.4120AF7B@Raytheon.com> X-Accept-Language: en,pdf Content-Type: text/plain; charset=us-ascii X-Complaints-To: Abuse Role , We Care X-Trace: newshog.newsread.com 956255231 216.14.8.65 (Thu, 20 Apr 2000 14:27:11 EDT) Organization: Telepath Systems (telepath.com) MIME-Version: 1.0 NNTP-Posting-Date: Thu, 20 Apr 2000 14:27:11 EDT Newsgroups: comp.lang.ada Date: 2000-04-20T00:00:00+00:00 List-Id: "Samuel T. Harris" wrote: > Any version control system which allows Fred to simply check-out > the file without warning him that his content is no longer > based on the latest version is seriously broken! This is a > basic access control feature. If you want this protection, > then support of this feature becames a primary tool selection > requirement! (Sigh). You are talking about a different revision control setup than I was in the quoted post (one in which the latest source is always visible, unless a local copy is checked out for editing). I addressed the (CVS) style you are referring to in another post. Suffice to say, the problem still exists in the setup you are talking about too (unless you have some kind of revision control system that notices that emacs has an obsolete copy loaded in its internal buffer). It seems like a lot of heat is getting generated on this issue due to misunderstandings about how different revision control systems work. The tragic part of this is that it doesn't matter at all what style of RCS you are using. We are *not* talking about external files here, but a buffer internal to emacs that never again gets checked against the file it was loaded from. No gyration done with external files can *possibly* solve this problem. Clearly the right solution to this problem (emacs checking the file for changes before writing it back out), has already been arrived at and implemented. So I don't see much point in continuing to sit here and argue over whether the problem exists. If the maintainer of the emacs ada mode saw that it exsits, and thought it was enough of a problem that it warranted fixing by the next revision, that's good enough for me. If anyone still feels compelled to continue this discussion, please at least do me the service of writing down your own scenario that shows how this won't be a problem. I feel like I'm swinging at the wind here. -- T.E.D. Home - mailto:dennison@telepath.com Work - mailto:dennison@ssd.fsi.com WWW - http://www.telepath.com/dennison/Ted/TED.html ICQ - 10545591