• Navigation überspringen
  • Zur Navigation
  • Zum Seitenende
Organisationsmenü öffnen Organisationsmenü schließen
Friedrich-Alexander-Universität Lehrstuhl für Informatik 4 (Systemsoftware)
  • FAUZur zentralen FAU Website
  1. Friedrich-Alexander-Universität
  2. Technische Fakultät
  3. Department Informatik
Suche öffnen
  • English
  • Campo
  • StudOn
  • FAUdir
  • Stellenangebote
  • Lageplan
  • Hilfe im Notfall
  1. Friedrich-Alexander-Universität
  2. Technische Fakultät
  3. Department Informatik
Friedrich-Alexander-Universität Lehrstuhl für Informatik 4 (Systemsoftware)
Menu Menu schließen
  • Lehrstuhl
    • Team
    • Aktuelles
    • Kontakt und Anfahrt
    • Leitbild
    • 50-jähriges Jubiläum
    Portal Lehrstuhl
  • Forschung
    • Forschungsbereiche
      • Betriebssysteme
      • Confidential Computing
      • Embedded Systems Software
      • Verteilte Systeme
    • Projekte
      • AIMBOS
      • BALu
      • BFT2Chain
      • DOSS
      • Mirador
      • NEON
      • PAVE
      • ResPECT
      • Watwa
    • Projektkampagnen
      • maRE
    • Seminar
      • Systemsoftware
    Portal Forschung
  • Publikationen
  • Lehre
    • Sommersemester 2025
      • Applied Software Architecture
      • Ausgewählte Kapitel der Systemsoftware
      • Betriebssystemtechnik
      • Projekt angewandte Systemsoftwaretechnik
      • System-Level Programming
      • Systemnahe Programmierung in C
      • Systemprogrammierung 1
      • Verteilte Systeme
    • Wintersemester 2025/26
      • Systemprogrammierung 2
      • Betriebssysteme
      • Middleware – Cloud Computing
      • Echtzeitsysteme
      • Virtuelle Maschinen
      • Web-basierte Systeme
      • Projekt angewandte Systemsoftwaretechnik
      • Aktuelle Entwicklung in Verteilten und Objektorientierten Betriebssystemen (für Bachelor-/Masterarbeit)
    Portal Lehre
  • Examensarbeiten
  1. Startseite
  2. Extern

Extern

Bereichsnavigation: Lehre
  • Betriebssysteme
    • Vorlesung
      • Folien
    • Übung
      • Seminar
      • Aufgaben
      • Aufgabe 0: C++ Streams
        • Aufgabe 1: Ein-/Ausgabe
          • Assembler Crashkurs
            • C++ Crashkurs
              • Entwicklungsumgebung
                • FAQ
                  • Ruhmeshalle

                Aufgabe 0: C++ Streams

                Graph Legend

                This page explains how to interpret the graphs that are generated by doxygen.

                Consider the following example:

                /*! Invisible class because of truncation */
                class Invisible { };
                /*! Truncated class, inheritance relation is hidden */
                class Truncated : public Invisible { };
                /* Class not documented with doxygen comments */
                class Undocumented { };
                /*! Class that is inherited using public inheritance */
                class PublicBase : public Truncated { };
                /*! A template class */
                template<class T> class Templ { };
                /*! Class that is inherited using protected inheritance */
                class ProtectedBase { };
                /*! Class that is inherited using private inheritance */
                class PrivateBase { };
                /*! Class that is used by the Inherited class */
                class Used { };
                /*! Super class that inherits a number of other classes */
                class Inherited : public PublicBase,
                protected ProtectedBase,
                private PrivateBase,
                public Undocumented,
                public Templ<int>
                {
                private:
                Used *m_usedClass;
                };

                This will result in the following graph:

                The boxes in the above graph have the following meaning:

                • A filled gray box represents the struct or class for which the graph is generated.
                • A box with a black border denotes a documented struct or class.
                • A box with a gray border denotes an undocumented struct or class.
                • A box with a red border denotes a documented struct or class forwhich not all inheritance/containment relations are shown. A graph is truncated if it does not fit within the specified boundaries.

                The arrows have the following meaning:

                • A dark blue arrow is used to visualize a public inheritance relation between two classes.
                • A dark green arrow is used for protected inheritance.
                • A dark red arrow is used for private inheritance.
                • A purple dashed arrow is used if a class is contained or used by another class. The arrow is labelled with the variable(s) through which the pointed class or struct is accessible.
                • A yellow dashed arrow denotes a relation between a template instance and the template class it was instantiated from. The arrow is labelled with the template parameters of the instance.
                Friedrich-Alexander-Universität
                Erlangen-Nürnberg

                Schlossplatz 4
                91054 Erlangen
                • Impressum
                • Datenschutz
                • Barrierefreiheit
                • Facebook
                • RSS Feed
                • Xing
                Nach oben