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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,deac256a05c84a59
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Marc A. Criley" <mcNOSPAM@mckae.com>
Newsgroups: comp.lang.ada
Subject: Re: DOM and SAX parsing in Ada
Date: Mon, 31 Jan 2005 08:24:18 -0600
Message-ID: <366tcfF4tp8fiU1@individual.net>
References: <41900010.D28DD400@boeing.com> <9CWjd.17305$5K2.1356@attbi_s03>
  <1106223415.857525.176640@c13g2000cwb.googlegroups.com>
  <gemini.iaoife001pbek00hc.nick.roberts@acm.org>
  <41F4DB6F.4090909@mailinator.com>
  <gemini.iavppg0091gj502zw.nick.roberts@acm.org>
 <35nh12F4oe4caU1@individual.net>
  <gemini.iawt1w000svx202ss.nick.roberts@acm.org>
  <UPWdnYp5d-1PFmrcRVn-rA@comcast.com>
  <gemini.iaxmj2001ydde00mw.nick.roberts@acm.org>
  <mailman.94.1106783306.527.comp.lang.ada@ada-france.org>
  <gemini.iazrta00fa0dd008g.nick.roberts@acm.org>
 <35t2u6F4qc335U1@individual.net>
  <gemini.iazxmw00jrr0d008g.nick.roberts@acm.org>
  <41fa4288$0$812$9b4e6d93@newsread2.arcor-online.net>
 <gemini.ib38yn003ldvl0314.nick.roberts@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net UyyZoT+TcIulPFtXOmaptg/GPgHoL0zRgKiOk05cO0Y59h8V/X
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
In-Reply-To: <gemini.ib38yn003ldvl0314.nick.roberts@acm.org>
Xref: g2news1.google.com comp.lang.ada:8087
Date: 2005-01-31T08:24:18-06:00
List-Id: <comp.lang.ada>

Nick Roberts wrote:
> Some systems do offer an 'untangle' facility, permitting changes made to the
> 'source' files (which are non-original in a traditional literate programming
> system) to be merged back into the source document files (which are the
> canonical originals). But this approach has certain dangers, and makes the
> overall system very complex.
> 
> I'm developing a 'reverse tangle' tool which takes this idea to the logical
> extreme of restoring the source code files back to their status as original
> files (intended to be edited by humans). This means that code changes can be
> made, and programs rebuilt and tested, using the traditional tool/IDE cycle
> (no need for any tangling). Reverse tangling is required when formatting the
> documentation, and the only literate programming tool required is the
> reverse tangle tool, which is way much simpler.

I'm not as up on literate programming as I could be, but I found some 
interesting, and I believe, related material in the article "Extensible 
Programming for the 21st Century":
  (http://www.acmqueue.org/modules.php?name=Content&pa=showpage&pid=247).

(The author suggests an XML representation of the "source code", so 
we're still on-topic in this thread :-)

Marc A. Criley
McKae Technologies
www.mckae.com