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,473e6b129c2f30cd
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII
Date: Mon, 11 Sep 2006 09:58:38 +0200
From: Manuel Collado <m.collado@fi.upm.es>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: ANNOUNCE: Avatox 1.0 is now available
References: <JaPEg.6886$Qf.5686@newsread2.news.pas.earthlink.net>
 <m2odudyfdm.fsf@grendel.local>
 <OA6Hg.840$bM.366@newsread4.news.pas.earthlink.net>
 <m264giacw2.fsf@grendel.local>
 <XfSdncT-efwBxGLZnZ2dnUVZ_tqdnZ2d@megapath.net>
 <m2u03jquay.fsf@grendel.local>
 <KfOdnRXjCaddSp3YnZ2dnUVZ_q6dnZ2d@megapath.net>
 <45018e97$0$17399$9b4e6d93@newsspool2.arcor-online.net>
 <45027b40@news.upm.es> <m23bb1s01k.fsf@grendel.local>
In-Reply-To: <m23bb1s01k.fsf@grendel.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: 138.100.242.204
Message-ID: <4505172d@news.upm.es>
X-Trace: 11 Sep 2006 09:58:37 +0100, 138.100.242.204
Path: 
 g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!130.59.10.21.MISMATCH!kanaga.switch.ch!switch.ch!news.rediris.es!news.upm.es!138.100.242.204
Xref: g2news2.google.com comp.lang.ada:6547
Date: 2006-09-11T09:58:38+02:00
List-Id: <comp.lang.ada>

Simon Wright escribi�:
> Manuel Collado <m.collado@fi.upm.es> writes:
> 
>> What puzzles me is that the XML structure (nesting) doesn't follows
>> the lexical Ada source structure. Example from avatox.adb -->
>> avatox.adb.xml:
>>
>> <A_CLAUSE ... startLine="29" endLine="29" startCol="1" endCol="29">
>>   <A_WITH_CLAUSE ... startLine="29" endLine="29" startCol="1" endCol="29"/>
>>   <AN_EXPRESSION ... startLine="29" endLine="29" startCol="6" endCol="28">
>>     <A_SELECTED_COMPONENT ... startLine="29" endLine="29" startCol="6"
>> endCol="28"/>
>>     <AN_EXPRESSION ... startLine="29" endLine="29" startCol="6" endCol="19">
>>       ....
>>
>> You can see that <A_WITH_CLAUSE> from (29,1) to (29,29) lexically
>> contains <AN_EXPRESSION> from (29,6) to (29,28). But the latest is not
>> nested inside the former. Instead, it appears as a sibling of it.
> 
> Marc and I disagree on this one. My approach in asis2xml is to have
> 
>     <context_clauses>
>       <with_clause>
>         <selected_component>
>           <selected_component>
>             <identifier>Ada</identifier>
>             <identifier>Characters</identifier>
>           </selected_component>
>           <identifier>Handling</identifier>
>         </selected_component>
>       </with_clause>
> 
> but it would be just as sensible to have
> 
>     <clause kind="with_clause">
> 
> The XPATH expressions aren't that different:
> 
>    A_CLAUSE[A_WITH_CLAUSE]
>    with_clause
>    clause[@kind='with_clause']
> 
> It depends what would be most useful. As an example of where user
> input would be good, what about that <selected_component> structure,
> which does follow the lexical structure of the language, but imagine
> the query to find all withs of Ada.Characters.Handling!

Well, the // (descendant) axis of XPATH looks directly for inner nodes, 
skipping intermediate levels.

-- 
Manuel Collado