Re: Should Inline be private in the private part of a package spec?

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

On 23.08.12 09:23, Dmitry A. Kazakov wrote:

> and XML stands in their way.

If XML stands in your way, OK. This seems to be about your nicely
integrated car networks where every party knows what to expect
and what to produce, and how to agree.
If you want to keep XML out of these internal, documented networks,
I totally agree with this.
But this is very specific to a situation that funds definitions
and agreements.

>> That's easier to see when there is
>> markup than when the program needs to guess

> Wasting time and memory.

So laborious guessing, looking for clues, is cheaper than just looking
at a tag that clearly identifies the intent of the tagged item?

Remember: in my networks I work more like an archaeologist trying
to understand the shards. That's easier when there are additional
hints like: found next to this one; has half a word printed on it.

> So it is the Excel's fault that XML requires parsing?

It feels too stupid to answer that again, sorry.
Roughly, N parsers > 1 parsers if N > 1. Roughly.

>>> Ada is not proposed for exchanging structured data
>>> between computers.
>>
>> It is, however, required to say how to exchange structured program
>> source text between compilers.
>
> No

Yes, it is. Character set support, documentation requirements, ...

Without what has become Ada, consider some 400 compilers and assemblers
translate programs written in some 400 different languages.
In order to transform them from some language to some target
language Ada, you need some 400 parsers. Or maybe, all would essentially
need to be compiled in the first place

Obviously, we need at least 1 parser even if only 1 programming
language remains.

Similarly, XML, or any agreed-upon way of exchanging data,
can remove some of the mess in data exchange, but will need
some kind of parsing. In any non-internal network.

>>> Ada is a programming language. XML in this context plays
>>> the role of a protocol to exchange above mentioned data.
>>
>> No. It is a markup language for tagging data in text documents.
>> We have been here before.
>
> That is it! XML is not for exchange of structured data.

No, XML is not a protocol for whatsoever.