禁止类继承的方法

Analyzing the problem

The problem is very simple: create a mechanism whereby it's possible to mark a class (say, NotABase) as being uninheritable, such that attempting to derive a class from that uninheritable class results in a compile-time error of some kind.

To achieve this behaviour we have to set up class NotABase so that it must do something that classes derived from it cannot do. That implies that we must make use of some property of base classes which is not inherited by their derived classes.

One such property is class friendship. If we made NotABase the only friend of some special class (say, Uninheritable) then no class derived from NotABase can (directly) access the private members of Uninheritable.

If we then arrange that those derived classes must access some such private member of Uninheritable, the derived classes immediately become invalid.

The most obvious way of making the derived classes access a private member of Uninheritable is to make Uninheritable's constructor private, and then make NotABase inherit Uninheritable. NotABase itself can call Uniheritable's private constructor (being a friend), but classes derived from NotABase cannot directly call that constructor (because the friendship isn't inherited).

Such an arrangement looks something like this:


class Uninheritable
{
friend class NotABase;
private:
Uninheritable(void) {}
};


class NotABase: public Uninheritable
{
// WHATEVER
};


class NotADerived: public NotABase
{
// WHATEVER ELSE
};

Unfortunately, this does not generate the hoped-for compile-time errors, because NotADerived's constructor only calls the (public) constructor for NotABase, which in turn calls the (private, but friendly-to-NotABase) constructor for Uninheritable. All of which is perfectly legal.

To make this idea work (or rather, to make it not work), we need to arrange for the constructor of NotADerived to try and call Uninheritable::Uninheritable() directly.


Virtual inheritance to the rescue

Fortunately, the rules of virtual inheritance (TDCS, § 12.1) require that a virtual base class's constructor is directly invoked by the most derived class. Hence, if Uninheritable were a virtual base class of NotABase, then the NotADerived constructor would have to call Uninheritable::Uninheritable() directly (rather than indirectly through NotABase) and the code would be invalid.

This is relatively easy to arrange - we simply make NotABase virtually inherit from Uninheritable:


class Uninheritable
{
friend class NotABase;
Uninheritable(void) {}
};


class NotABase: virtual public Uninheritable
{
// WHATEVER
};


class NotADerived: public NotABase
{
// WHATEVER ELSE
};

Now NotADerived (or any other class derived from NotABase!) is obliged to call the Uninheritable constructor directly, which it can't do, not being a friend. Therefore classes derived from NotABase can never compile.


Generalizing Uninheritable

The above technique works well provided we only ever want to make one class (namely, NotABase) uninheritable. If we want to create many such classes we need a more general solution.

What we would like is a mechanism that automatically creates special "Uninheritable-like" classes to order. These special classes would declare friendship to the specific classes which were to be made uninheritable, and those specific classes would then become uninheritable by virtually inheriting from the automatically-generated "Uninheritable-like" classes (!)

This merry-go-round of class relationships is reminiscent of the class hierarchy in "Topic 4: Self Linking Lists", and the solution - "recursive" inheritance through a template - is the same:


template <class OnlyFriend>
class Uninheritable
{
friend class OnlyFriend;
Uninheritable(void) {}
};


class NotABase : virtual public Uninheritable<NotABase>
{
// WHATEVER
};


class NotADerived: public NotABase
{
// THIS CLASS GENERATES A COMPILER ERROR
};


class AnotherUninheritable
: virtual public Uninheritable<AnotherUninheritable>
{
// WHATEVER
};


// ETC.

Now, to create a class X which cannot be inherited from, we simply ensure that X (virtually) inherits from Uninheritable<X>.

Note that classes like Uninheritable (and SelfLinking) are known as mixins¤, because they "mix-in" some additional useful property, independent from any other behaviour of the class which inherits them.

一、综合实战—使用极轴追踪方式绘制信号灯 实战目标:利用对象捕捉追踪和极轴追踪功能创建信号灯图形 技术要点:结合两种追踪方式实现精确绘图,适用于工程制图中需要精确定位的场景 1. 切换至AutoCAD 操作步骤: 启动AutoCAD 2016软件 打开随书光盘中的素材文件 确认工作空间为"草图与注释"模式 2. 绘图设置 1)草图设置对话框 打开方式:通过"工具→绘图设置"菜单命令 功能定位:该对话框包含捕捉、追踪等核心绘图辅助功能设置 2)对象捕捉设置 关键配置: 启用对象捕捉(F3快捷键) 启用对象捕捉追踪(F11快捷键) 勾选端点、中心、圆心、象限点等常用捕捉模式 追踪原理:命令执行时悬停光标可显示追踪矢量,再次悬停可停止追踪 3)极轴追踪设置 参数设置: 启用极轴追踪功能 设置角度增量为45度 确认后退出对话框 3. 绘制信号灯 1)绘制圆形 执行命令:"绘图→圆→圆心、半径"命令 绘制过程: 使用对象捕捉追踪定位矩形中心作为圆心 输入半径值30并按Enter确认 通过象限点捕捉确保圆形位置准确 2)绘制直线 操作要点: 选择"绘图→直线"命令 捕捉矩形上边中点作为起点 捕捉圆的上象限点作为终点 按Enter结束当前直线命令 重复技巧: 按Enter可重复最近使用的直线命令 通过圆心捕捉和极轴追踪绘制放射状直线 最终形成完整的信号灯指示图案 3)完成绘制 验证要点: 检查所有直线是否准确连接圆心和象限点 确认极轴追踪的45度增量是否体现 保存绘图文件(快捷键Ctrl+S)
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值