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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,254d058bd7de11b3 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Writing changelog entries Date: 04 Jan 2005 21:02:13 -0500 Organization: Cuivre, Argent, Or Message-ID: References: <87y8f96imj.fsf@deneb.enyo.de> <87wtus3do0.fsf@deneb.enyo.de> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: melchior.cuivre.fr.eu.org 1104890548 8923 212.85.156.195 (5 Jan 2005 02:02:28 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Wed, 5 Jan 2005 02:02:28 +0000 (UTC) To: comp.lang.ada@ada-france.org Return-Path: In-Reply-To: <87wtus3do0.fsf@deneb.enyo.de> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Path: g2news1.google.com!news1.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!oleane.net!oleane!feed.ac-versailles.fr!usenet-fr.net!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail Xref: g2news1.google.com comp.lang.ada:7455 Date: 2005-01-04T21:02:13-05:00 Florian Weimer writes: > Many projects have explicit guidelines which ensure that you can > grep the changelog and find the change which affected a particular > entity. I never use a changelog for that. In fact, I never do that. But I guess I haven't been involved in a large project where that would be necessary; all my projects are small enough that I know what's going on anyway, by keeping up with daily CVS updates. > However, these guidelines are C-specific and do not take homographs > into account (and neither nested subprograms, and so on). Right. Hmm. You want a CM tool that can answer the query: what changes affected . I don't know of any CM tools that do that directly; it would require the CM tool to understand the language. In Ada, every name can be spelled uniquely; for overloaded functions you need to include the parameter/result profile, etc. So you could have a style guide that says "when checking in changes, include the _unique_ name of every item affected". Yuck; that would be a huge burden on the programmers. You could write an ASIS tool to generate that name list by comparing the two versions of the file; you can have CVS run that tool and append the result to the checkin comment. Hmm. Getting both versions into one ASIS context would be tricky; you'd need a top level namespace for each version. Whether that's worth doing depends on how often you do this query, and how important it is. Hmm. You could have the CM tool generate the diffs for each change, and then grep that for . That might be efficient, but it doesn't address the homograph issue. -- -- Stephe