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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: "G.B." <bauhaus@futureapps.invalid>
Newsgroups: comp.lang.ada
Subject: Re: What is the best license to use for open source software?
Date: Thu, 29 Jan 2015 15:41:04 +0100
Organization: A noiseless patient Spider
Message-ID: <madgov$dp6$1@dont-email.me>
References: <8f389b7e-31e8-48ea-98c4-cd4471db9293@googlegroups.com>
 <1w1u3p8o0pf3u.5fidvp7gla8x$.dlg@40tude.net> <mad1qr$glu$1@dont-email.me>
 <bhi2awb4u5pa.1i02k97hclunz$.dlg@40tude.net>
Reply-To: nonlegitur@futureapps.de
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 29 Jan 2015 14:40:31 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="b96887e80893c84a90c3007226ca0d1c";
	logging-data="14118"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18KJBbTSp7tAXCjQ/8qJ13HfXbF236DDmc="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
In-Reply-To: <bhi2awb4u5pa.1i02k97hclunz$.dlg@40tude.net>
Cancel-Lock: sha1:AWZ5OTbIVyT+ma7UGTuk2EGl1Cw=
Xref: news.eternal-september.org comp.lang.ada:24795
Date: 2015-01-29T15:41:04+01:00
List-Id: <comp.lang.ada>

On 29.01.15 14:19, Dmitry A. Kazakov wrote:
> The idea is to check as much as possible. E.g. HTML tags with parameters
> like <img> would be mapped onto Ada subprograms with corresponding typed
> parameters (src, alt, height, width).

Almost all attempts at equating web applications and forms
programming have failed in one way or other.

And on the conceptual side: for a start, targeting "web devices",
one does not usually want _any_ style related instructions in
"business logic", hence no height, no width in Ada source text;
also, one doesn't want any i18n in source text, so you'd have
to introduce indirection to resources outside Ada in any case.

The typing issue cannot be solved practically, because
the "hardware" (browsers) is inconsistent WRT the "language",
leading to contradictory interpretations. Trying to tackle
the inconsistency by case distinction is hard, if at all
possible.