From: "Vasiliy Molostov" <molostoff@gmail.com>
Subject: Re: questions on Ada openGL binding in the GLOBE3D packages
Date: Thu, 02 Aug 2012 16:12:17 +0400
Date: 2012-08-02T16:12:17+04:00 [thread overview]
Message-ID: <op.wiexirrska8ora@aspire.local> (raw)
In-Reply-To: 501a6ad4$0$6553$9b4e6d93@newsspool4.arcor-online.net
Georg Bauhaus <rm.dash-bauhaus@futureapps.de> писал(а) в своём письме Thu,
02 Aug 2012 15:56:03 +0400:
> On 02.08.12 13:12, Egil Høvik wrote:
>>> Why not keep things standard? The standard is there.
> It there a strong technical argument in favor of
> using package software in stead of names implying
> packages? Better visibility control? Better compilation
> performance due to separation? Better change management
> by modularization?
Do we need use name prefixes while having high level tools
to organize imported procedures in a way we decide by self?
Prefix is a C "necessity", and when imported it then has nothing common
with C.
It seems, that a good binding can provide many benefits when imports being
organized in an ada-way, only if you are not going to provide
low-level direct 1:1 mapping to what people use in C.
Is there a benefit using 1:1 C in Ada?
--
Написано в почтовом клиенте браузера Opera: http://www.opera.com/mail/
next prev parent reply other threads:[~2012-08-06 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jvddr3$uqm$1@speranza.aioe.org>
2012-08-02 8:50 ` questions on Ada openGL binding in the GLOBE3D packages Egil Høvik
2012-08-02 9:14 ` Nasser M. Abbasi
2012-08-02 10:19 ` Niklas Holsti
2012-08-02 10:46 ` Nasser M. Abbasi
2012-08-02 11:12 ` Egil Høvik
2012-08-02 11:56 ` Georg Bauhaus
2012-08-02 12:12 ` Vasiliy Molostov [this message]
2012-08-02 12:01 ` Vasiliy Molostov
2012-08-02 21:12 ` Randy Brukardt
2012-08-02 20:59 ` Randy Brukardt
2012-08-02 12:13 ` Brian Drummond
2012-08-02 15:01 ` Robert A Duff
2012-08-02 21:18 ` Randy Brukardt
2012-08-02 23:15 ` Robert A Duff
2012-08-02 15:31 ` Pascal Obry
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox