From: wolf Date: Fri, 6 Sep 2002 22:06:34 +0000 (+0000) Subject: Remove forward declaration files. X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9f1da968a08a1c223fd955eec7ad382c223460c0;p=dealii-svn.git Remove forward declaration files. git-svn-id: https://svn.dealii.org/trunk@6371 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/news/2002/c-3-4.html b/deal.II/doc/news/2002/c-3-4.html index 1563bac598..66d60425f0 100644 --- a/deal.II/doc/news/2002/c-3-4.html +++ b/deal.II/doc/news/2002/c-3-4.html @@ -33,6 +33,33 @@ contributor's names are abbreviated by WB (Wolfgang Bangerth), GK

General

    +
  1. + Removed: The forward declarations files have gone. We have never + propagated their use in the example programs, but these files have been + there in the base, lac, and grid include directories, and forward + declared all classes that were present in the respective parts of the + library. This, the idea was, enables you to use just this include file + in your own header files, rather than including the full declarations of + these classes. However, maintaining these forward declaration files has + been a constant thorn in our side, be it that the timing of their + generation was difficult when using parallel builds, or that they were + difficult to generate at first. The latter is now the reason for their + abolition: we had a script for their generation, but it did not take + into account namespaces, so we got clashes when we found that we had + used the same class name in two different namespaces, since the script + put the forward declaration incorrectly into the global namespace where + they conflicted. Since we do not plan to extend the script by a + parser that can properly handle opening and closing braces of + namespaces, we simply drop these files. +
    + What you should do if you have used these forward declaration files: you + have two possibilities - either include the respective header file in + which the class is fully declared, or write the forward declaration into + your headers yourself. +
    + (WB 2002/09/05) +

    +
  2. New: There is now a new report