chap12 operator overload

 
两种方式

(1)friend function

//xxx.h
class Integer {
 long i;
public:
 Integer(long ll = 0) : i(ll) {}

 friend const Integer operator+(const Integer& left,const Integer& right);
 //对于输入输出只能用这种方式
 friend ostream& operator<<(ostream& os, const Integer& in);
};

//xxx.cpp
const Integer operator+(const Integer& left,const Integer& right)
{
 return Integer(left.i + right.i);
}

ostream& operator<<(ostream& os, const Integer& in)
{
 os<<in.i<<endl;
 return os;
}

(2)member function
//xxx.h
class Integer {
 long i;
public:
 Integer(long ll = 0) : i(ll) {}

 const Integer operator+(const Integer& right)
 {
return Integer(i + right.i):
 }
};

推荐:

Operator               Recommended use
-------------------------------------------------------------------------
All unary operators                  member
-------------------------------------------------------------------------
= ( ) [ ] –> –>*               must be member
-------------------------------------------------------------------------
+= –= /= *= ^=
&= |= %= >>= <<=                      member
-------------------------------------------------------------------------
All other binary operators                  non-member
-------------------------------------------------------------------------



参数和返回值设定

As with any function argument, if you only need to read from the argument and not change
it, default to passing it as a const reference. Ordinary arithmetic operations (like +
and –, etc.) and Booleans will not change their arguments, so pass by const reference is
predominantly what you’ll use. When the function is a class member, this translates to
making it a const member function. Only with the operator-assignments (like +=) and the
operator=, which change the left-hand argument, is the left argument not a constant, but

it’s still passed in as an address because it will be changed.
The type of return value you should select depends on the expected meaning of the operator.
(Again, you can do anything you want with the arguments and return values.) If the effect
of the operator is to produce a new value, you will need to generate a new object as the
return value. For example, Integer: :operator+ must produce an Integer object that is the
sum of the operands. This object is returned by value as a const, so the result cannot be
modified as an lvalue.

All the assignment operators modify the lvalue. To allow the result of the assignment to
be used in chained expressions, like a=b=c, it’s expected that you will return a reference
to that same lvalue that was just modified. But should this reference be a const or
nonconst? Although you read a=b=c from left to right, the compiler parses it from right to
left, so you’re not forced to return a nonconst to support assignment chaining. However,
people do sometimes expect to be able to perform an operation on the thing that was just
assigned to, such as (a=b).func( ); to call func( ) on a after assigning b to it. Thus,
the return value for all of the assignment operators should be a nonconst reference to the
lvalue.

For the logical operators, everyone expects to get at worst an int back, and at best a bool.
(Libraries developed before most compilers supported C++’s built-in bool will use int or
an equivalent typedef.)


返回值的优化

(1)return Integer(left.i + right.i)
(2)Integer tmp(left.i + right.i);
  return tmp;
第二种方式下,先调用构造函数得到对象tmp,然后调用拷贝构造函数,将tmp拷贝改返回值,最后调用
析构函数销毁tmp,而第一种方式下,直接调用构造函数得到返回值,效率高了很多!

In contrast, the “returning a temporary” approach works quite differently. When the
compiler sees you do this, it knows that you have no other need for the object it’s
creating than to return it. The compiler takes advantage of this by building the object
directly into the location of the outside return value. This requires only a single
ordinary constructor call (no copy-constructor is necessary) and there’s no destructor
call because you never actually create a local object. Thus, while it doesn’t cost
anything but programmer awareness, it’s significantly more efficient. This is often
called the return value optimization.


赋值与拷贝构造函数

MyType b;
MyType a = b;//调用copy ctor
a = b;//调用operator=

区分:如果一个对象没有初始化,那么调用copy ctor,如果已经初始化了,则调用operator=



Reflexivity

One of the most convenient reasons to use global overloaded operators instead of member
operators is that in the global versions, automatic type conversion may be applied to
either operand, whereas with member objects, the left-hand operand must already be the
proper type. If you want both operands to be converted, the global versions can save a lot
of coding. Here’s a small example:


//: C12:ReflexivityInOverloading.cpp
class Number {
 int i;
public:
 Number(int ii = 0) : i(ii) {}
 const Number
 operator+(const Number& n) const {
   return Number(i + n.i);
 }
 friend const Number
   operator-(const Number&, const Number&);
};

const Number
 operator-(const Number& n1,
           const Number& n2) {
   return Number(n1.i - n2.i);
}

int main() {
 Number a(47), b(11);
 a + b; // OK
 a + 1; // 2nd arg converted to Number
//! 1 + a; // Wrong! 1st arg not of type Number
 a - b; // OK
 a - 1; // 2nd arg converted to Number
 1 - a; // 1st arg converted to Number
} ///:~
Class Number has both a member operator+ and a friend operator–. Because there’s a
constructor that takes a single int argument, an int can be automatically converted to a
Number, but only under the right conditions. In main( ), you can see that adding a Number
to another Number works fine because it’s an exact match to the overloaded operator. Also,
when the compiler sees a Number followed by a + and an int, it can match to the member
function Number: :operator+ and convert the int argument to a Number using the constructor.
But when it sees an int, a +, and a Number, it doesn’t know what to do because all it has
is Number: :operator+, which requires that the left operand already be a Number object. Thus,
the compiler issues an error.


With the friend operator–, things are different. The compiler needs to fill in both its
arguments however it can; it isn’t restricted to having a Number as the left-hand argument.
Thus, if it sees

1 – a
it can convert the first argument to a Number using the constructor.
源码来自:https://pan.quark.cn/s/7a757c0c80ca 《在Neovim中运用Lua的详尽教程》在当代文本编辑器领域,Neovim凭借其卓越的性能、可扩展性以及高度可定制的特点,赢得了程序开发者的广泛青睐。 其中,Lua语言的融入更是为Neovim注入了强大的活力。 本指南将深入剖析如何在Neovim中高效地运用Lua进行配置和插件开发,助你充分发挥这一先进功能的潜力。 一、Lua为何成为Neovim的优选方案经典的Vim脚本语言(Vimscript)虽然功能完备,但其语法结构与现代化编程语言相比显得较为复杂。 与此形成对比的是,Lua是一种精简、轻量且性能卓越的脚本语言,具备易于掌握、易于集成的特点。 因此,Neovim选择Lua作为其核心扩展语言,使得配置和插件开发过程变得更加直观和便捷。 二、安装与设置在Neovim中启用Lua支持通常十分简便,因为Lua是Neovim的固有组件。 然而,为了获得最佳体验,我们建议升级至Neovim的最新版本。 可以通过`vim-plug`或`dein.vim`等包管理工具来安装和管理Lua插件。 三、Lua基础在着手编写Neovim的Lua配置之前,需要对Lua语言的基础语法有所掌握。 Lua支持变量、函数、控制流、表(类似于数组和键值对映射)等核心概念。 它的语法设计简洁明了,便于理解和应用。 例如,定义一个变量并赋值:```lualocal myVariable = "Hello, Neovim!"```四、Lua在Neovim中的实际应用1. 配置文件:Neovim的初始化文件`.vimrc`能够完全采用Lua语言编写,只需在文件首部声明`set runtimepath^=~/.config/nvim ini...
基于STM32 F4的永磁同步电机无位置传感器控制策略研究内容概要:本文围绕基于STM32 F4的永磁同步电机(PMSM)无位置传感器控制策略展开研究,重点探讨在不使用机械式位置传感器的情况下,如何通过算法实现对电机转子位置和速度的精确估算与控制。文中结合STM32 F4高性能微控制器平台,采用如滑模观测器(SMO)、扩展卡尔曼滤波(EKF)或高频注入法等先进观测技术,实现对电机反电动势或磁链的实时估算,进而完成磁场定向控制(FOC)。研究涵盖了控制算法设计、系统建模、仿真验证(可能使用Simulink)以及在嵌入式平台上的代码实现与实验测试,旨在提高电机驱动系统的可靠性、降低成本并增强环境适应性。; 适合人群:具备一定电机控制理论基础和嵌入式开发经验的电气工程、自动化及相关专业的研究生、科研人员及从事电机驱动开发的工程师;熟悉C语言和MATLAB/Simulink工具者更佳。; 使用场景及目标:①为永磁同步电机驱动系统在高端制造、新能源汽车、家用电器等领域提供无位置传感器解决方案的设计参考;②指导开发者在STM32平台上实现高性能FOC控制算法,掌握位置观测器的设计与调试方法;③推动电机控制技术向低成本、高可靠方向发展。; 其他说明:该研究强调理论与实践结合,不仅包含算法仿真,还涉及实际硬件平台的部署与测试,建议读者在学习过程中配合使用STM32开发板和PMSM电机进行实操验证,以深入理解控制策略的动态响应与鲁棒性问题。
先看效果: https://pan.quark.cn/s/21391ce66e01 企业级办公自动化系统,一般被称为OA(Office Automation)系统,是企业数字化进程中的关键构成部分,旨在增强组织内部的工作效能与协同水平。 本资源提供的企业级办公自动化系统包含了详尽的C#源代码,涉及多个技术领域,对于软件开发者而言是一份极具价值的参考资料。 接下来将具体介绍OA系统的核心特性、关键技术以及在实践操作中可能涉及的技术要点。 1. **系统构造** - **三层构造**:大型OA系统普遍采用典型的三层构造,包含表现层、业务逻辑层和数据访问层。 这种构造能够有效分离用户交互界面、业务处理过程和数据存储功能,从而提升系统的可维护性与可扩展性。 2. **C#编程语言** - **C#核心**:作为开发语言,C#具备丰富的类库和语法功能,支持面向对象编程,适用于开发复杂的企业级应用。 - **.NET Framework**:C#在.NET Framework环境中运行,该框架提供了大量的类库与服务,例如ASP.NET用于Web开发,Windows Forms用于桌面应用。 3. **控件应用** - **WinForms**或**WPF**:在客户端,可能会使用WinForms或WPF来设计用户界面,这两者提供了丰富的控件和可视化设计工具。 - **ASP.NET Web Forms/MVC**:对于Web应用,可能会使用ASP.NET的Web Forms或MVC模式来构建交互式页面。 4. **数据库操作** - **SQL Server**:大型OA系统通常采用关系型数据库管理系统,如SQL Server,用于存储和处理大量数据。 - **ORM框架**:如Ent...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值