10.4 Members

Namespaces和各类成员介绍
博客主要介绍了Namespaces和各类类型(如struct、enumeration、class等)的成员情况。Namespaces和类型有成员,类型成员可声明或继承。不同类型继承情况有别,如类继承基类时部分构造函数和析构函数不继承,且继承成员可能因访问性或隐藏问题不可用。
10.4 Members
Namespaces and types have members. [Note: The members of an entity are
generally available through the
use of a qualified name that starts with a reference to the entity,
followed by a ... token, followed by the
name of the member. end note]
Members of a type are either declared in the type or inherited from the
base class of the type. When a type
inherits from a base class, all members of the base class, except instance
constructors, destructors, and static
constructors become members of the derived type. The declared accessibility
of a base class member does
not control whether the member is inherited.inheritance extends to any
member that isn.t an instance
constructor, static constructor, or destructor. However, an inherited
member may not be accessible in a
derived type, either because of its declared accessibility (§10.5.1) or
because it is hidden by a declaration in
the type itself (§10.7.1.2).
10.4.1 Namespace members
Namespaces and types that have no enclosing namespace are members of the
global namespace. This
corresponds directly to the names declared in the global declaration space.
Namespaces and types declared within a namespace are members of that
namespace. This corresponds
directly to the names declared in the declaration space of the namespace.
Namespaces have no access restrictions. It is not possible to declare
private, protected, or internal
namespaces, and namespace names are always publicly accessible.
10.4.2 Struct members
The members of a struct are the members declared in the struct and the
members inherited from the struct.s
direct base class System.ValueType and the indirect base class object.
The members of a simple type correspond directly to the members of the
struct type aliased by the simple
type:
. The members of sbyte are the members of the System.SByte struct.
. The members of byte are the members of the System.Byte struct.
. The members of short are the members of the System.Int16 struct.
. The members of ushort are the members of the System.UInt16 struct.
. The members of int are the members of the System.Int32 struct.
. The members of uint are the members of the System.UInt32 struct.
. The members of long are the members of the System.Int64 struct.
Chapter 10 Basic concepts
73
. The members of ulong are the members of the System.UInt64 struct.
. The members of char are the members of the System.Char struct.
. The members of float are the members of the System.Single struct.
. The members of double are the members of the System.Double struct.
. The members of decimal are the members of the System.Decimal struct.
. The members of bool are the members of the System.Boolean struct.
10.4.3 Enumeration members
The members of an enumeration are the constants declared in the enumeration
and the members inherited
from the enumeration.s direct base class System.Enum and the indirect base
classes System.ValueType
and object.
10.4.4 Class members
The members of a class are the members declared in the class and the
members inherited from the base class
(except for class object which has no base class). The members inherited
from the base class include the
constants, fields, methods, properties, events, indexers, operators, and
types of the base class, but not the
instance constructors, destructors, and static constructors of the base
class. Base class members are inherited
without regard to their accessibility.
A class declaration may contain declarations of constants, fields, methods,
properties, events, indexers,
operators, instance constructors, destructors, static constructors, and
types.
The members of object and string correspond directly to the members of the
class types they alias:
. The members of object are the members of the System.Object class.
. The members of string are the members of the System.String class.
10.4.5 Interface members
The members of an interface are the members declared in the interface and
in all base interfaces of the
interface. [Note: The members in class object are not, strictly speaking,
members of any interface (§20.2).
However, the members in class object are available via member lookup in any
interface type (§14.3). end
note]
10.4.6 Array members
The members of an array are the members inherited from class System.Array.
10.4.7 Delegate members
The members of a delegate are the members inherited from class
System.Delegate.
Bridge eVIDX Multicast Group A packet forwarded to a Multicast port group is assigned an index call “eVIDX”. The eVIDX represents a multi-target group, consisting of physical ports and ePorts (Section 4.3, Extended VIDX (eVIDX)). A registered Multicast packet is assigned an eVIDX from the bridge Multicast FDB entry (Section 10.4.1.2, FDB Multicast Entry). Unknown Unicast and unregistered non-IP Multicast and Broadcast packets are assigned to an eVIDX based on the eVLAN table entry fields: <Flood eVIDX Mode> and <Flood eVIDX>. The <Flood eVIDX Mode> has the following modes:  Assign <Flood eVIDX> from the eVLAN entry for non-IP Unregistered Multicast only; Broadcast and Unknown Unicast packets are assigned eVIDX = 0xFFF which implies flooding the packet to all eVLAN physical port members.  Apply <Flood eVIDX> from eVLAN entry for ALL flooded traffic (non-IP Unregistered Multicast, Broadcast, Unknown Unicast). By default, this field is set to 0xFFF which implies flooding the packet to all eVLAN port members. Unregistered IP Multicast packets are assigned to an eVIDX based on the eVLAN table entry fields: <Flood eVIDX>, <Unregistered IPM eVIDX> and <Unregistered IPM eVIDX mode>. If <Unregistered IPM eVIDX> = 0 assign <Flood eVIDX> from the eVLAN entry for Unregistered IP Multicast, otherwise use the <Unregistered IPM eVIDX mode> to determine the eVIDX value for Unregistered IP Multicast packets. The <Unregistered IPM eVIDX mode> has the following modes:  Assign <Unregistered IPM eVIDX> from the eVLAN entry for Unregistered IP Multicast.  Assign <Unregistered IPM eVIDX> from the eVLAN entry for Unregistered IPv4 Multicast, and assign <Flood eVIDX> from the eVLAN entry for Unregistered IPv6 Multicast  Assign <Flood eVIDX> from the eVLAN entry for Unregistered IPv4 Multicast, and assign <Unregistered IPM eVIDX> from the eVLAN entry for Unregistered IPv6 Multicast  Assign <Unregistered IPM eVIDX> from the eVLAN entry for Unregistered IPv4 Multicast, and assign <Unregistered IPM eVIDX> +1 from the eVLAN entry for Unregistered IPv6 Multicast The L2MLL (Section 15.2, IP/L2-Multicast Linked List (MLL) Replicator Engines) resolves the eVIDX to a list of ePorts and to a VIDX. The VIDX serves as a direct index into the bridge Multicast table. Each entry in the bridge Multicast table contains a physical port map of the Multicast group member ports on the local device At initialization the VIDX Multicast table is cleared to all zeros, with the exception of an entry for VIDX 0xFFF, which is initialized to have all physical ports as members. This enables Multicast packets to be flooded to all the VLAN physical ports. The Multicast table entry 0xFFF must not be modified by the CPU. To perform bridge VLAN Egress filtering for physical ports, the VIDX port map is AND’ed with the VID port map, ensuring that the Egress ports are members of the packet VLAN group assignment. It is a configurable option to disable VLAN Egress filtering for multi-target packets with specific VIDX Configuration  To configure the VIDX Multicast Group Table, configure the Multicast Groups Table (Table 920 p. 2903).  To disable VLAN Egress filtering for multi-target packets with specific VIDX (I.e. with VIDX<>0xFFF) set the <Independent Non Flood VIDX Enable> field in the Global Configurations Register (Table 887 p. 2821 翻译并解释 (with VIDX<>0xFFF)
11-18
翻译: BSS operation To control the operation of stations on an HT BSS, the AP uses the HT Operation element. To control the operation of stations on a VHT BSS, the AP uses both the HT Operation element and the VHT Operation element. These elements may be present in Beacon, Probe Response, Association Response, and Reassociation Response frames. Details on the HT Operation element and VHT Operation element can be found in Sections 12.3.2.3 and 12.3.2.8, respectively. To establish the BSS operating channels and operating channel width, the AP uses the following fields in the HT Operations element: * Primary Channel. This field gives the channel number of the primary 20MHz channel for the BSS. * Secondary Channel Offset. This field gives the offset of the secondary 20MHz channel relative to the primary 20MHz channel. * STA Channel Width. This field defines the channel widths with which HT stations may transmit. Options are 20MHz or 40MHz. In addition, for VHT operation, the AP uses the following fields in the VHT Operation element: * Channel Width. This field, together with the STA Channel Width field in the HT Operation element, defines the channel widths with which VHTstations may transmit. Options are: 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz. * Channel Center Frequency Index 0. This field defines the center frequency for an 80MHz or 160MHz BSS. For an 80+80MHz BSS, this field defines the center frequency for the lower frequency segement. * Channel Center Frequency Index 1. For an 80+80MHz BSS, this field defines the center frequency for the upper frequency segment. The APalso provides information on the capabilities of stations that are members of the BSS or, optionally, detected operating in the same channel(s). This allows member stations to determine the level of protection required for frame sequences the station may use but for which a nearby station may not defer correctly. The fields in the HT Operation element that provide information on nearby stations for the purpose of enabling protection are the following: * HTProtection.Thisindicates the types of stations that are present as members or non members of the BSSandthus the nature of the protection required. Four categories are distinguished as listed in Table 11.1. * Non-Greenfield HT STAs Present. This indicates that there are HT stations associ ated with the BSS that are unable to receive HT Greenfield format PPDUs. When set, associated stations must protect HT Greenfield format transmissions. * L-SIG TXOPProtection Full Support. This indicates whether or not all stations on the BSS support L-SIG TXOP Protection. A station may use this to decide whether or not to use L-SIG TXOP Protection. * OBSS Non-HT STAs Present. This indicates that there may be non-HT stations present that are not members oftheBSS.Astation mayoptionallyusethis todetermine if protection is necessary for HT sequences. * RIFS Mode. The AP can directly control whether or not RIFS bursting is permitted through the RIFSModebit.StationsmayonlyuseRIFSburstingwhenthisbitissetto1. AVHTAPalwayssets this bit to 0, preventing the use of RIFS. * DSSS/CCKModein40MHz.ThisindicateswhetherornotmemberstationsoftheBSS are permitted to transmit DSSS/CCK format PPDUs during 20/40MHz BSS operation. The HT Operation element also provides information for controlling PSMP operation (see Section 10.4), phased coexistence operation (see Section 11.4) and the use of Dual Beacons to extend range. Finally, the Basic MCSSet field inthe HTOperationelementand theVHTBasicMCS Set field in the VHT Operation element provide the set of MCS values that are supported by all HTstations and VHTstations, respectively, in the BSS.
08-20
【最优潮流】直流最优潮流(OPF)课设(Matlab代码实现)内容概要:本文档主要围绕“直流最优潮流(OPF)课设”的Matlab代码实现展开,属于电力系统优化领域的教学与科研实践内容。文档介绍了通过Matlab进行电力系统最优潮流计算的基本原理与编程实现方法,重点聚焦于直流最优潮流模型的构建与求解过程,适用于课程设计或科研入门实践。文中提及使用YALMIP等优化工具包进行建模,并提供了相关资源下载链接,便于读者复现与学习。此外,文档还列举了大量与电力系统、智能优化算法、机器学习、路径规划等相关的Matlab仿真案例,体现出其服务于科研仿真辅导的综合性平台性质。; 适合人群:电气工程、自动化、电力系统及相关专业的本科生、研究生,以及从事电力系统优化、智能算法应用研究的科研人员。; 使用场景及目标:①掌握直流最优潮流的基本原理与Matlab实现方法;②完成课程设计或科研项目中的电力系统优化任务;③借助提供的丰富案例资源,拓展在智能优化、状态估计、微电网调度等方向的研究思路与技术手段。; 阅读建议:建议读者结合文档中提供的网盘资源,下载完整代码与工具包,边学习理论边动手实践。重点关注YALMIP工具的使用方法,并通过复现文中提到的多个案例,加深对电力系统优化问题建模与求解的理解。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值