comp.lang.ada
 help / color / mirror / Atom feed
From: Victor Porton <porton@narod.ru>
Subject: Re: Encaspulation: What to export
Date: Wed, 29 Nov 2017 20:46:27 +0200
Date: 2017-11-29T20:46:27+02:00	[thread overview]
Message-ID: <ovmva2$1q20$1@gioia.aioe.org> (raw)
In-Reply-To: ovkod5$7s6$1@franka.jacob-sparre.dk

Randy Brukardt wrote:

> "Victor Porton" <porton@narod.ru> wrote in message
> news:ovjv01$1r5c$1@gioia.aioe.org...
>> Randy Brukardt wrote:
>>
>>> "Victor Porton" <porton@narod.ru> wrote in message
>>> news:ovhst9$1a43$1@gioia.aioe.org...
>>> ...
>>>> I parse not a string but an RDF tree. It is similar to convert AST
>>>> (abstract
>>>> syntax tree) to another format. RDF is similar to an AST but more
>>>> abstract.
>>>>
>>>> So it is NOT a deserialization operation in Ada sense.
>>>
>>> Calling the operation of creating an RDF (or XML or HTML or SGML ...)
>>> tree
>>> from "parsing" is a gross distortion from what really is going on. As
>>
>> No. I "parse" RDF (not a text file) and create data in other format.
> 
> Yes, you (do something, but don't parse) RDF and create some other format.
> Format transformations surely don't require parsing. My objection is that
> what you are doing to create that other format is not parsing; it's rather
> just a text to tree transformation that is deterministic (really a very

It is not text to tree transformation.

It is a transformation from a tree (in fact a directed graph) into another 
format. (This digraph is created parsing a text file, but this is a 
different story, because I use already ready binding of a C library to parse 
a text format into RDF graph.)

Transformation from tree is very similar to parsing (yes, I use this word) 
from an abstract syntax tree to another format.

When reading an AST, the word "parsing" is correct, despite it is not in any 
way text parsing.

I do use the word "parsing" because it uses techniques very similar to text 
parsing, namely I use recursive descent.

> simple state machine). Calling that "parsing" trivializes the much more
> complex languages that parsers can make sense of. None of the on-line
> languages (with the possible exception of CSS) require any parsing; SGML
> was designed to not require parsing and all of these other formats kept
> the basic design of SGML.
> 
>                                           Randy.
-- 
Victor Porton - http://portonvictor.org


  parent reply	other threads:[~2017-11-29 18:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 19:25 Encaspulation: What to export Victor Porton
2017-11-27 20:00 ` Dmitry A. Kazakov
2017-11-27 20:34   ` Victor Porton
2017-11-27 20:35     ` Victor Porton
2017-11-28  2:12     ` Randy Brukardt
2017-11-28 15:22       ` Victor Porton
2017-11-28 22:36         ` Randy Brukardt
2017-11-28 23:29           ` Shark8
2017-11-29  4:44             ` gautier_niouzes
2017-11-29 20:32               ` Randy Brukardt
2017-11-29 21:08                 ` gautier_niouzes
2017-11-30 21:42                   ` Randy Brukardt
2017-11-29  8:40             ` Dmitry A. Kazakov
2017-11-29  7:31           ` G. B.
2017-11-29  7:38             ` G. B.
2017-11-29  8:14             ` Simon Wright
2017-11-29 18:46           ` Victor Porton [this message]
2017-11-29 19:43             ` Dmitry A. Kazakov
2017-11-29 19:57               ` Victor Porton
2017-11-29 20:42             ` Randy Brukardt
2017-11-29 22:18               ` Shark8
2017-11-27 21:39 ` Simon Wright
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox