Log4cxx
  1. Log4cxx
  2. LOGCXX-33

log4cxx::Exception is not derived from std::exception

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.7
    • Fix Version/s: 0.10.0
    • Component/s: None
    • Labels:
      None

      Description

      Raised by Tommi Mäkitalo in http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-dev@logging.apache.org&msgNo=313 with follow up discussion in thread.

      Boost guidelines on exceptions: http://www.boost.org/more/error_handling.html

      I've reworked the exceptions so they derive from std::exception and getMessage() just repackages the value returned by std::exception::what. Added new exceptions classes that override std::exception::what() for exceptions with fixed messages. Exceptions with variable messages were either simplified to return static messages or had getMessage overriden to generate equivalent message on request. PlatformSocketException and MissingBraceException are instances of that latter. Also changed use of non-threadsafe stderror to strerror_r in SocketException.

        Activity

        Curt Arnold made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Curt Arnold made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Curt Arnold created issue -

          People

          • Assignee:
            Curt Arnold
            Reporter:
            Curt Arnold
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development