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

["Randy Brukardt" <randy@rrsoftware.com>]

"Britt" <britt.snodgrass@gmail.com> wrote in message 
news:50677fa2-7f82-4ccc-8c56-161bf67fefe1@googlegroups.com...
On Thursday, August 9, 2012 5:39:32 PM UTC-4, Randy Brukardt wrote:

>> I detest the idea of separate project files like GPR; most of that
>> information should have been in the Ada source (having it there makes the
>> code more portable to other Ada implementations). The need for
>> meta-languages always shows a lack in the original language.

>I think GPR files are fabulous. I see them as a well designed framework for 
>managing
> the development and build process. Almost all of the information that goes 
> in GPR files
> is about project structure (e.g. file locations), settings for GNAT's 
> ASIS-based tools,
> and some IDE options. I don't really see any overlap with information I 
> would want
> to put in source code.

This is "information" that you shouldn't have to put anywhere at all - it's 
just cruft that is needed because of poor mappings to the underlying system. 
Better systems in the future won't use most of this stuff, it will alll 
happen automatically.

I've recently talked to several customers that don't use any sort of 
sophisticated project management at all: they simply make a new directory 
and populate it with the contents of version control when anything needs to 
change. (One of these customers was managing several thousand files this 
way). Then, they just point the build tools at it and go -- no complex 
project files needed (or wanted). They thought that complex project 
organizations just added complications on modern hardware, and I tend to 
agree. (The recompilation time they would save with shared files is probably 
less than the time that they would spend on managing the projects.)

YMMV, of course, but I think "one-button builds" from raw (and portable) 
source code is the ideal way to go. I'm now looking at ways to make that 
easier with Janus/Ada (one obvious way is to eliminate the need for any 
special naming conventions for Ada source code).

                                               Randy.