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,b2011d0de07e01d2 X-Google-Attributes: gid103376,public From: Wes Groleau Subject: Re: wanted: Ada diff tool Date: 2000/05/04 Message-ID: <3911A245.67F8DEE1@ftw.rsc.raytheon.com>#1/1 X-Deja-AN: 619195590 Content-Transfer-Encoding: 7bit References: <8eot2o$kbm$1@wanadoo.fr> <030520002201489719%nospam@nospam.com> X-Accept-Language: en,es,fr,pt Content-Type: text/plain; charset=us-ascii X-Complaints-To: news@ext.ray.com X-Trace: bos-service2.ext.raytheon.com 957456971 151.168.144.162 (Thu, 04 May 2000 12:16:11 EDT) Organization: Raytheon Company MIME-Version: 1.0 NNTP-Posting-Date: Thu, 04 May 2000 12:16:11 EDT Newsgroups: comp.lang.ada Date: 2000-05-04T00:00:00+00:00 List-Id: > case where lines with embedded carrage control. if you change the > formatting on lines it won't do a true diff. to make this a true > normalize it needs to convert every ada statement into a single line. I once wrote a tool that converted an Ada program to one lexical token per line, upper cased. Gave a true semantic diff capability, but the results were awfully hard to read! The CompLite/CompTig tool recently mentioned looks like an excellent solution. -- Wes Groleau http://freepages.genealogy.rootsweb.com/~wgroleau