HardenedBSD/contrib/kyua/utils/fs/exceptions.hpp
Brooks Davis b0d29bc47d Import the kyua test framework.
Having kyua in the base system will simplify automated testing in CI and
eliminates bootstrapping issues on new platforms.

The build of kyua is controlled by WITH(OUT)_TESTS_SUPPORT.

Reviewed by:	emaste
Obtained from:	CheriBSD
Sponsored by:	DARPA
Differential Revision:	https://reviews.freebsd.org/D24103
2020-03-23 19:01:23 +00:00

111 lines
3.6 KiB
C++

// Copyright 2010 The Kyua Authors.
// All rights reserved.
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions are
// met:
//
// * Redistributions of source code must retain the above copyright
// notice, this list of conditions and the following disclaimer.
// * Redistributions in binary form must reproduce the above copyright
// notice, this list of conditions and the following disclaimer in the
// documentation and/or other materials provided with the distribution.
// * Neither the name of Google Inc. nor the names of its contributors
// may be used to endorse or promote products derived from this software
// without specific prior written permission.
//
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
/// \file utils/fs/exceptions.hpp
/// Exception types raised by the fs module.
#if !defined(UTILS_FS_EXCEPTIONS_HPP)
#define UTILS_FS_EXCEPTIONS_HPP
#include <stdexcept>
#include <string>
namespace utils {
namespace fs {
/// Base exception for fs errors.
class error : public std::runtime_error {
public:
explicit error(const std::string&);
virtual ~error(void) throw();
};
/// Error denoting an invalid path while constructing a fs::path object.
class invalid_path_error : public error {
/// Raw value of the invalid path.
std::string _textual_path;
public:
explicit invalid_path_error(const std::string&, const std::string&);
virtual ~invalid_path_error(void) throw();
const std::string& invalid_path(void) const;
};
/// Paths cannot be joined.
class join_error : public error {
/// Raw value of the first path in the join operation.
std::string _textual_path1;
/// Raw value of the second path in the join operation.
std::string _textual_path2;
public:
explicit join_error(const std::string&, const std::string&,
const std::string&);
virtual ~join_error(void) throw();
const std::string& textual_path1(void) const;
const std::string& textual_path2(void) const;
};
/// Exceptions for errno-based errors.
///
/// TODO(jmmv): This code is duplicated in, at least, utils::process. Figure
/// out a way to reuse this exception while maintaining the correct inheritance
/// (i.e. be able to keep it as a child of fs::error).
class system_error : public error {
/// Error number describing this libc error condition.
int _original_errno;
public:
explicit system_error(const std::string&, const int);
~system_error(void) throw();
int original_errno(void) const throw();
};
/// Exception to denote an unsupported operation.
class unsupported_operation_error : public error {
public:
explicit unsupported_operation_error(const std::string&);
virtual ~unsupported_operation_error(void) throw();
};
} // namespace fs
} // namespace utils
#endif // !defined(UTILS_FS_EXCEPTIONS_HPP)