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
X-Google-Thread: 103376,39bde956b245c191
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Received: by 10.68.14.100 with SMTP id o4mr491878pbc.6.1323107437600;
        Mon, 05 Dec 2011 09:50:37 -0800 (PST)
Path: 
 lh20ni72775pbb.0!nntp.google.com!news1.google.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: How to nicely distribute a simple Ada library?
Date: Mon, 5 Dec 2011 18:50:34 +0100
Organization: cbb software GmbH
Message-ID: <1djnmk0kgl65q$.1vbfo4w0hv7lt.dlg@40tude.net>
References: <slrnjdmlq0.1lme.lithiumcat@sigil.instinctive.eu>
 <361x89sndsg9$.16ruxrwxud090$.dlg@40tude.net>
 <op.v50l7yalule2fv@douda-yannick> <pp4kgx5l3a9o$.5e4ysumkwde2.dlg@40tude.net>
 <op.v50sd4xgule2fv@douda-yannick>
 <4edce1ab$0$6552$9b4e6d93@newsspool4.arcor-online.net>
 <op.v50w0tw8ule2fv@douda-yannick>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: M/A383hIGz+44RAnbocmcQ.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news1.google.com comp.lang.ada:19355
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Date: 2011-12-05T18:50:34+01:00
List-Id: <comp.lang.ada>

On Mon, 05 Dec 2011 16:51:55 +0100, Yannick Duchêne (Hibou57) wrote:

> Le Mon, 05 Dec 2011 16:22:19 +0100, Georg Bauhaus  
> <rm.dash-bauhaus@futureapps.de> a écrit:
>> Another reason is obfuscation. Where do you find the build
>> settings for this software?  Somewhere in the sources.
>> […]
> I see three advantages for this: first this is  
> clearly visible from body source (especially if specified at the top of  
> the source) and then,

Which body? The option is seen in the gnatmake/gprbuild string. If an
inappropriate option appears there, your actions? If a desired option does
not, how do you find the body missing it?

> this applies localization principle (lack of  
> localization does not help understanding), and then again, if this package  
> is not used, then the linker option is automatically dropped (avoid  
> unneeded dependencies).

Normally, linker options do not apply to the bodies, they do to the program
as a whole.

> If multiple package links to the same library,  
> there is no troubles anyway.

That depends on the option. If conflicting options appear, good luck in
resolving the problem.

> The only one issue I know is linker dependency. The pragma Linker_Options  
> arguments syntax is not specified by the standard.

Yes, the compiler has all rights to ignore it. So you would definitely
enjoy gathering linker options spread across all *used* bodies guessing
what was ignored and what was taken...

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de