From 8d0fa13b025e8128e6453991c5dae17946d2fb9d Mon Sep 17 00:00:00 2001
From: Nadeem <nadeem.shehzad@desy.de>
Date: Fri, 28 Feb 2020 10:12:59 +0100
Subject: [PATCH] removed non essential and non sense comments.

---
 doc/exceptionHandlingDesign.dox | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/doc/exceptionHandlingDesign.dox b/doc/exceptionHandlingDesign.dox
index c060e83a..5fe72375 100644
--- a/doc/exceptionHandlingDesign.dox
+++ b/doc/exceptionHandlingDesign.dox
@@ -140,12 +140,6 @@ Implmentation.
 - ExceptionHandlingDecorator
 - TriggerFanOut
 
-Additional note from code author.
-Note that if the data is distributed through a triggered FanOut (i.e. variables from device is connected to other variables through a trigger, the usual way for poll-type variables) the data read from the receiving end of the variable cannot be considered valid if the DataValidity is faulty.
-Additionaly, a change of to a faulty validity state will signal the availability of new data on those variables, which is to be considered invalid.
-
-
-Bahnhof.Variables which are Constants or outputs of the ConfigReader and are connected to a DeviceModule should be written in an initialisation handler. Currently they are written in ConfigReader::pepare() etc., which might block the application initialisation if an exception occurs in the process of writing these variables.
 
 -<b>8. Initialise the device after recovey.</b>
 
-- 
GitLab