From 66abbed5e08370412b81be1628590898ceeeb604 Mon Sep 17 00:00:00 2001
From: Michele Calgaro <michele.calgaro@yahoo.it>
Date: Sat, 29 May 2021 19:05:31 +0900
Subject: Renaming of files in preparation for code style tools.

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
---
 Documentation/ConduitProgrammingTutorial/index.tex | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'Documentation/ConduitProgrammingTutorial/index.tex')

diff --git a/Documentation/ConduitProgrammingTutorial/index.tex b/Documentation/ConduitProgrammingTutorial/index.tex
index 35bdc00..909df86 100644
--- a/Documentation/ConduitProgrammingTutorial/index.tex
+++ b/Documentation/ConduitProgrammingTutorial/index.tex
@@ -217,9 +217,9 @@ service_DATA = mal_conduit.desktop
 kde_module_LTLIBRARIES = libmalconduit.la
 
 libmalconduit_la_SOURCES = \
-        mal-factory.cc \
-        mal-setup.cc \
-        mal-conduit.cc \
+        mal-factory.cpp \
+        mal-setup.cpp \
+        mal-conduit.cpp \
         mal-setup_dialog.ui
 libmalconduit_la_LDFLAGS = $(KDE_RPATH) -L../../lib
 libmalconduit_la_LIBADD = -lkpilot $(MAL_LIB)
@@ -281,7 +281,7 @@ always returns a pointer to a \class{KLibFactory} instance. Whenever a program n
 the conduit, it calls the \code{createObject} of the \class{KLibFactory} to get an appropriate object.
 Furthermore, the conduit factory initializes the about dialog of the conduit. 
 
-The factories of all conduits are very similar, so you best just copy the .h and .cc file of an existing conduit 
+The factories of all conduits are very similar, so you best just copy the .h and .cpp file of an existing conduit 
 for your conduit. All you need to do is to change the copyright notices for the about dialog, and 
 change the class names of the \class{ConduitAction} and \class{ConduitSetup} to your own class names. Also, 
 the factory is a good place to define the strings for the config settings' entries to the config file.
@@ -297,7 +297,7 @@ private:
 } ;
 \end{verbatim}
 }
-and in the .cc file
+and in the .cpp file
 {\small\begin{verbatim}
 const char*MALConduitFactory::fConfigSetting1="NameOfSetting";
 \end{verbatim}
@@ -311,7 +311,7 @@ Everything else in the factory can stay as it is.
 Here is an example of the malsync's factory:
 \begin{htmlonly}
   \htmladdnormallink{Source code of mal-factory.h}{mal-factory.h}
-  \htmladdnormallink{Source code of mal-factory.cc}{mal-factory.cc}
+  \htmladdnormallink{Source code of mal-factory.cpp}{mal-factory.cpp}
 \end{htmlonly}
 
 
@@ -320,9 +320,9 @@ Here is an example of the malsync's factory:
 {\scriptsize
  \verbatiminput{mal-factory.h}
 }
-\subsubsection{mal-factory.cc}
+\subsubsection{mal-factory.cpp}
 {\scriptsize
- \verbatiminput{mal-factory.cc}
+ \verbatiminput{mal-factory.cpp}
 }
 \end{latexonly}
 
-- 
cgit v1.2.3

