The exception class named castor::exception::Exception provides the same
functionality as castor::exception::Internal and therefore one of them
had to go for the sake of removing redundant code.

Renamed typoed, non unwritten rules following dlg_pengindMessagesVector class to castor::dlf::PendingMessagesVector.

Added cleanup in the pending list of the c++ version of the library (for cases when dlf_init is not called.

Changed the handling of logmasks. Now the configuration is always queried and the source is respected

This involved moving the definition of basic exceptions to the libcastorcommon and thus adding dependencies to this library in a couple of places that depended only on libcastorclient

  - added includes for string.h and stdlib.h
  - added casts from const char* to char*

This macro should be used when it is desirable to include the file, line and
function context information in a log.  It is advised to include such
information when logging an error for the developers, but not to use it for
monitoring logs where operators are informed of what is happening and they do
not need or want to know the details of the source code.

The CASTOR_DLF_WRITEPC macro macro generates the file, line and function
context information automatically and passes it on down the DLF logging chain.
This means developers do not need to use the __FILE__, __LINE__,
__PRETTY_FUNCTION__ macros in their application code when logging.  Here is an
example of using this macro:

  try {
    ...
  } catch(castor::exception::Exception &ex) {
    castor::dlf::Param params[] = {
      castor::dlf::Param("volReqId", vdqmJobRequest.tapeRequestId),
      castor::dlf::Param("Message" , ex.getMessage().str()       ),
      castor::dlf::Param("Code"    , ex.code()                   )};
    CASTOR_DLF_WRITEPC(cuuid, DLF_LVL_ERROR, AGGREGATOR_MAIN_SELECT_FAILED,
      params);
  }

of ::dlf_init() to the exception thrown by:

castor::dlf::dlf_init(const char* facilityName, castor::dlf::Message messages[])

A nice explanatory message was being consructed when the facility name exceeded
21 characters in length, but the message was not added to the exception, so I
only got a "Unable to initialize DLF" with no further explanation when I tried
to initialise DLF with a crazy long name.

Use ::dlf_isinitialized instead of our own version so that it works also when DLF is initialized from C

Improved logging into DLF. You can now declare new messages even before DLF was initialized. Very useful for libraries loaded before the main is called \!

C++ interface to DLF. This is supposed to replace the current logging facility without loosing the possibility to give objects to the interface.