关于 exception 的一个问题# Programming - 葵花宝典
r*r
1 楼
class exception
{
public:
exception() throw() { }
virtual ~exception() throw();
virtual const char* what() const throw();
};
问题: 为什么 what() 返回一个 const char * 类型?
为什么不返回一个 string 呢? 可以返回一个 string 吗?
class exception
{
public:
exception() throw() { }
virtual ~exception() throw();
virtual const char* what() const throw();
};
问题: 为什么 what() 返回一个 const char * 类型?
为什么不返回一个 string 呢? 可以返回一个 string 吗?
t*t
2 楼
what if string throw another exception?
【在 r*********r 的大作中提到】
:中定义了 class exception:
: class exception
: {
: public:
: exception() throw() { }
: virtual ~exception() throw();
: virtual const char* what() const throw();
: };
: 问题: 为什么 what() 返回一个 const char * 类型?
: 为什么不返回一个 string 呢? 可以返回一个 string 吗?
【在 r*********r 的大作中提到】
:
: class exception
: {
: public:
: exception() throw() { }
: virtual ~exception() throw();
: virtual const char* what() const throw();
: };
: 问题: 为什么 what() 返回一个 const char * 类型?
: 为什么不返回一个 string 呢? 可以返回一个 string 吗?
r*r
3 楼
但是 logic_error 和 runtime_error 都有 data member 是 string 类型.
也就是说你 throw 一个 runtime_error object 时, 要作 string 的 copy
construction,
这样也有可能 throw another exception
也就是说你 throw 一个 runtime_error object 时, 要作 string 的 copy
construction,
这样也有可能 throw another exception
t*t
4 楼
well, the standard only says the interface (there's no obligation on data
members). implementation can do whatever they like to do...
【在 r*********r 的大作中提到】
: 但是 logic_error 和 runtime_error 都有 data member 是 string 类型.
: 也就是说你 throw 一个 runtime_error object 时, 要作 string 的 copy
: construction,
: 这样也有可能 throw another exception
members). implementation can do whatever they like to do...
【在 r*********r 的大作中提到】
: 但是 logic_error 和 runtime_error 都有 data member 是 string 类型.
: 也就是说你 throw 一个 runtime_error object 时, 要作 string 的 copy
: construction,
: 这样也有可能 throw another exception
r*r
5 楼
well, the standard says logic_error's interface is like this:
class logic_error : public exception
{
public:
explicit logic_error(const string& __arg);
}
hard to imagine an implementation that can actually avoid copying __arg.
can you?
class logic_error : public exception
{
public:
explicit logic_error(const string& __arg);
}
hard to imagine an implementation that can actually avoid copying __arg.
can you?
t*t
6 楼
no, i can't explain now. hehe.
【在 r*********r 的大作中提到】
: well, the standard says logic_error's interface is like this:
: class logic_error : public exception
: {
: public:
: explicit logic_error(const string& __arg);
: }
: hard to imagine an implementation that can actually avoid copying __arg.
: can you?
:
【在 r*********r 的大作中提到】
: well, the standard says logic_error's interface is like this:
: class logic_error : public exception
: {
: public:
: explicit logic_error(const string& __arg);
: }
: hard to imagine an implementation that can actually avoid copying __arg.
: can you?
:
r*r
7 楼
i came up with an idea: define a char * data member x;
and do the following in the constructor:
x = (char *)malloc(__arg.size());
strcpy(x, __arg.c_str());
and return x in what(), and call free(x) in the destructor.
maybe that works, at least it's guaranteed that no additional exception will
be thrown.
and do the following in the constructor:
x = (char *)malloc(__arg.size());
strcpy(x, __arg.c_str());
and return x in what(), and call free(x) in the destructor.
maybe that works, at least it's guaranteed that no additional exception will
be thrown.
相关阅读
古赵=书生，魏=范进，月光xuer=市井地痞新年快乐说点技术之外的话题：2份全工clojurescript 一年回顾求助，window10下安装不了armadillo库java fluent api 底层是怎么实现的？maven一问赌约在此AMT啥意思？看不懂啊科学家:满嘴脏话的人词汇量更大 编程能力更好(图)客户端给你们算了这个牛掰，看看那个videoASIO异步一问好虫 那8000多伪币自杀前能发包子散了吗？我是否需要Move(C++11)?docker和vagrant的异同是啥，大家都用哪个12306 细节我老人家从来说话算数求推荐tech stackJSONCPP和ASIO能否联合使用(C++11)？