blocks|key|311462|text|你可以像下面这样使用(未编译)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|311463|class+Date+{
private:
int+day;
int+month;
int+year;
int+daysPerMonth[];
public:
Date(+int+day,+int+month,+int+year+)+{
++++int+daysPerMonth[12]+=+{31,28,31,30,31,30,31,31,30,31,30,31};

++++if(isValidDate(day,+month,+year))+
++++{
++++++++this->day+=+day;
++++++++this->month+=+month;
++++++++this->year+=+year;
++++}+else+{
++++++++throw+std::string("No+valid+input+date+numbers...");//what+i+throw???
++++++++}
++++}
};

int+main()
{
+try{
++++Date+d(55,223,0122);
++}
+catch(std::string+&e)
+{
++++//+Do+necessary+handling
++}
}|code-block|syntax|javascript|311464|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use Like this below (Not compiled):-

<pre><code>class Date {
private:
int day;
int month;
int year;
int daysPerMonth[];
public:
Date( int day, int month, int year ) {
 int daysPerMonth[12] = {31,28,31,30,31,30,31,31,30,31,30,31};

 if(isValidDate(day, month, year)) 
 {
 this-&gt;day = day;
 this-&gt;month = month;
 this-&gt;year = year;
 } else {
 throw std::string("No valid input date numbers...");//what i throw???
 }
 }
};

int main()
{
 try{
 Date d(55,223,0122);
 }
 catch(std::string &amp;e)
 {
 // Do necessary handling
 }
}
</code></pre>

blocks|key|620616|text|在C%2B%2B中，你可以抛出任何类型的对象。通常是std::exception或从它派生的类型，但也可以是其他任何类型。例如，MFC或_com_error中的CException与std::exception没有任何关系。不管你扔什么，你都要接住同样的东西。(您不能在抛出std::string的同时捕获std::exception。)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|620617|entityMap^0|M|E|1S|A|24|A|2F|E|3P|B|45|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|G|$]]

In C++ you can throw objects of any type. Usually that is <code>std::exception</code> or a type derived from it, but it can be anything else. For instance <code>CException</code> in MFC or <code>_com_error</code> have nothing to do with <code>std::exception</code>. Regardless what you throw you must catch the same. (You cannot throw a <code>std::string</code> and catch a <code>std::exception</code>.)

blocks|key|303012|text|C%2B%2B允许你throw任何类型的值(包括基础类型)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|303013|try+{
++++throw+42;
}+catch(int+e)+{
++++std::cout+<<+"Caught:+"+<<+e+<<+"\n";
}|code-block|syntax|javascript|303014|但与C%2B%2B中的许多其他事情一样，仅仅因为您可以做到这一点，并不意味着您应该这样做。|303015|这里的usual+advice是以某种方式抛出从std::exception派生的专用异常对象。也就是说，如果抛出的类型不应该在其他上下文中使用。如果要将某个值与异常相关联，请构建一个将该值作为成员包含的异常包装类，而不是直接抛出该值的类型。|303016|这个建议的基本原理是，您希望构建一个异常层次结构，允许在不同的通用层次上捕获:如果我对确切的异常类型不感兴趣，我只捕获std::exception；如果我只想处理某些类型的错误，我会在异常层次结构的更低层捕获一个派生类。|303017|如果您保持异常类型与程序中使用的其他类型不同，则这样的异常层次结构更易于维护和推理。此外，这个指导方针使人们不那么容易滥用异常作为美化的返回值，这是你永远不应该做的事情。|303018|entityMap|0|LINK|mutability|MUTABLE|url|http://www.parashift.com/c%2B%2B-faq/what-to-throw.html^0|6|5|0|0|0|O|E|3|C|0|0|1N|E|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|O|3|P|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1E|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

C++ allows you to <code>throw</code> values of any type (including fundamental types).

<pre><code>try {
 throw 42;
} catch(int e) {
 std::cout &lt;&lt; "Caught: " &lt;&lt; e &lt;&lt; "\n";
}
</code></pre>

But as with many other things in C++, just because you can do it, does not mean you should do it.

The <a href="http://www.parashift.com/c++-faq/what-to-throw.html" rel="nofollow">usual advice</a> here is to throw dedicated exception objects deriving from <code>std::exception</code> in some way. That is, if a types that are thrown should not be used in other contexts. If you want to associate a certain value with an exception, build an exception wrapper class that contains that value as a member, instead of throwing the value's type directly.

The rationale for this advice is that you want to build an exception hierarchy that allows catching at different layers of generality: If I'm not interested in the exact kind of exception I just catch <code>std::exception</code>; if I only want to handle certain kinds of errors, I instead catch a derived class further down the exception hierarchy.

Such exception hierarchies are much easier to maintain and reason about if you keep exception types distinct from the other types used in your program. Also, this guideline makes it less tempting for people to abuse exceptions as glorified return values, which is something you should never do.

I made strange code, but surprisingly it works. But now I don't know what I throw and how can I catch it:

<pre><code>class Date {
private:
 int day;
 int month;
 int year;
 int daysPerMonth[];
public:
 Date( int day, int month, int year ) {
 int daysPerMonth[12] = {31,28,31,30,31,30,31,31,30,31,30,31};

 if(isValidDate(day, month, year)) {
 this-&gt;day = day;
 this-&gt;month = month;
 this-&gt;year = year;
 } else {
 throw std::string("No valid input date numbers...");//what i throw???
 }
 }
</code></pre>

Please help me with code.

Throw and catch std::string

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我写了一些奇怪的代码，但令人惊讶的是它还能工作。但现在我不知道我抛出了什么，我怎么才能接住它：class Date {private:    int day;    int month;    int year;    int daysPerMonth[];public:    Date( int day, int m...

问抛出并捕获std::string
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问抛出并捕获std::stringEN