On 29 Apr., 00:03, Francis Glassborow
<francis.glassbo...@[EMAIL PROTECTED]
> wrote:
> With respect, that is not something I would ever choose to 'safely
> assume'. Many programmers spend time wanting to save time :) Complete
> rebuilds for large projects are things to leave for natural breaks (over
> lunch, over-night and, I suppose in extreme cases, over a weekend though
> I have never come across a project where that was necessary)
I agree that some programmers lost more time in finding an optimal
solution than worth it:-)
But fact is, that it is really annoying if compilation takes too long
time. You cannot always have a lunch break just at the moment you want
to sync your workspace and compile:)
> Note that IBM had a C++ compiler that effectively did something like the
> OP's proposal but that was a decade ago. The problem with it was that it
> was inherently non-standard and no way to fix it to make it standard
> conforming.
Sure, this 'trick' is nothing I would do as a standard tool or even
for us but regarding the whole project. But as the components remain
separate and the component owners are responsible about their
functions and namespaces, they can check compilation (and
functionality) of their module.
> When I write code in a .cpp file using an unnamed namespace I
> am assuming that the names I use there are not going to leak out (though
> I think there are now some implications if I have a compiler that uses
> ex****t). The unnamed namespace of a .cpp file being written by me is
> mine and I should not have to spend time worrying about possible naem
> conflicts with code in other files (other than those I explicitly
include)
Yes, this _may_ result in an advice to not use unnamed namespaces or
being sensible using them across cpps in _your_ module/component
(which is the same as the CU in this case).
Of course, minimizing your include statements is the goal, but hard to
maintain with a lot of files and developers. I.e. we want to get rid
of fat headers (like windows.h or the ones mentioned by Andre) in
typical project include headers.
Peter Holtwick
--
[ See http://www.gotw.ca/resources/clcm.htm
for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]
|
