comp.lang.ada
 help / color / mirror / Atom feed
From: "Dan'l Miller" <optikos@verizon.net>
Subject: Re: Trouble translating a C++ data-structure.
Date: Mon, 12 Mar 2018 09:07:40 -0700 (PDT)
Date: 2018-03-12T09:07:40-07:00	[thread overview]
Message-ID: <f95625ed-ee06-43f4-aa04-6720d33efc1d@googlegroups.com> (raw)
In-Reply-To: <7a285484-20b5-475e-b252-113b8a803785@googlegroups.com>

shark8 wrote:
> What do you mean by "top level posting"? 

New posting to comp.lang.ada, not a reply.

> Well, I'm aiming for it to be not only HIGHLY portable, but extremely modular/maintainable.

Which portions of GNAT are not “HIGHLY portable” for example?

On an entirely different topic in the 2nd half of the sentence above, the ultimate in “extreme modular”ity would be to remove all control-flow/looping/branching constructs from the core language, ‘reducing’ them to ‘mere’ libraries, as Alphard was pursuing in the 1970s.  Something similar could be done throughout other constructs in Ada, such as the specs, so that the core language is an extremely small language and Ada-as-we-know-it, Ada+Spark-as-we-know-it, Ada+ASIS-as-we-know-it, Ada+newFangledInnovations-yet-to-be-imagined, and so forth are •libraries•—not of subroutines & parameterized-types/generics, but of Ada-Reference-Manual semantics & syntax and so forth, much as Alphard at Carnegie Mellon University was envisioning back in the 1970s:  basically to back-apply more-modern concepts:  aspect-oriented programming (AOP) weavers on steroids.  Or in other words, what if the Ada Reference Manual was no longer English prose, but rather executable Alphard-esque code.  What if a stage of multi-stage programming was to compile the app's chosen weaving of Ada83 or Ada95 or Ada2012 or Ada+Spark or Ada+ASIS or Ada+somethingEvenMoreWow?  (Mary Shaw had a breakthrough in the making, but never finished it during the late 1970s, apparently because Greed/Red/Ada sucked all the air out of the room, leaving little budget/time/research-grants for Alphard.)  Now that truly would be the breakthrough for compiler front-ends that LLVM has been for compiler back-ends.  That would put Ada back in the driver's seat as the premier processor-native-machine-code compiled language, leap-frogging & eclipsing Clang as the perceived most-modern truly state-of-the-art among all the (open-source) compiler front-ends.  Plus, such multistage-programming modularity in the compiler front-end would unleash an explosion of new language evolution/extension in Ada (just when many people outside the Ada community think Ada is getting old & grey-haired needing to go to bed early each evening due to being out of energy each day).  It might even usher in an era of fervor for Ada unseen since the DoD chose Green over Red.

Or did you have something else in mind as “extreme modular”ity of an Ada front-end?

  parent reply	other threads:[~2018-03-12 16:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  0:37 Trouble translating a C++ data-structure Shark8
2018-03-08  0:49 ` Paul Rubin
2018-03-08  2:33 ` gautier_niouzes
2018-03-09 16:24 ` Dan'l Miller
2018-03-09 22:44   ` Shark8
2018-03-10  3:02     ` Bojan Bozovic
2018-03-10 12:45       ` Bojan Bozovic
2018-03-10 18:10         ` Shark8
2018-03-12 16:07     ` Dan'l Miller [this message]
2018-03-12 23:46     ` Randy Brukardt
2018-03-12 19:49 ` Mehdi Saada
2018-03-12 22:26   ` Shark8
2018-03-13  1:22   ` Paul Rubin
2018-03-13  2:11   ` Dan'l Miller
2018-03-13 19:51     ` Paul Rubin
2018-03-13 23:35       ` Dan'l Miller
2018-03-14  4:28         ` Dan'l Miller
2018-03-14  3:14       ` Shark8
2018-03-14  4:44         ` Bojan Bozovic
2018-03-14  5:10           ` Paul Rubin
replies disabled

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