分享
 
 
 

14.5.2 Simple names

王朝other·作者佚名  2006-02-28
窄屏简体版  字體: |||超大  

A simple-name consists of a single identifier.

simple-name:

identifier

A simple-name is evaluated and classified as follows:

?If the simple-name appears within a block and if the block?s (or an

enclosing block?s) local variable

declaration space (?0.3) contains a local variable or parameter with the

given name, then the simplename

refers to that local variable or parameter and is classified as a variable.

?Otherwise, for each type T, starting with the immediately enclosing

class, struct, or enumeration

declaration and continuing with each enclosing outer class or struct

declaration (if any), if a member

lookup of the simple-name in T produces a match:

If T is the immediately enclosing class or struct type and the lookup

identifies one or more methods, the

result is a method group with an associated instance expression of this.

If T is the immediately enclosing class or struct type, if the lookup

identifies an instance member, and if the

reference occurs within the block of an instance constructor, an instance

method, or an instance accessor, the

result is the same as a member access (?4.5.4) of the form this.E, where E

is the simple-name.

Otherwise, the result is the same as a member access (?4.5.4) of the form

T.E, where E is the simple-name.

In this case, it is a compile-time error for the simple-name to refer to an

instance member.

?Otherwise, starting with the namespace in which the simple-name occurs,

continuing with each

enclosing namespace (if any), and ending with the global namespace, the

following steps are evaluated

until an entity is located:

If the namespace contains a namespace member with the given name, then the

simple-name refers to that

member and, depending on the member, is classified as a namespace or a type.

Otherwise, if the namespace has a corresponding namespace declaration

enclosing the location where the

simple-name occurs, then:

?If the namespace declaration contains a using-alias-directive that

associates the given name with

an imported namespace or type, then the simple-name refers to that

namespace or type.

?Otherwise, if the namespaces imported by the using-namespace-directives

of the namespace

declaration contain exactly one type with the given name, then the

simple-name refers to that

type.

?Otherwise, if the namespaces imported by the using-namespace-directives

of the namespace

declaration contain more than one type with the given name, then the

simple-name is ambiguous

and a compile-time error occurs.

?Otherwise, the name given by the simple-name is undefined and a

compile-time error occurs.

14.5.2.1 Invariant meaning in blocks

For each occurrence of a given identifier as a simple-name in an expression

or declarator, every other

occurrence of the same identifier as a simple-name in an expression or

declarator within the immediately

Chapter 14 Expressions

139

enclosing block (?5.2) or switch-block (?5.7.2) must refer to the same

entity. [Note: This rule ensures that

the meaning of a name is always the same within a block. end note]

[Example: The example

class Test

{

double x;

void F(bool b) {

x = 1.0;

if (b) {

int x = 1;

}

}

}

results in a compile-time error because x refers to different entities

within the outer block (the extent of

which includes the nested block in the if statement). In contrast, the

example

class Test

{

double x;

void F(bool b) {

if (b) {

x = 1.0;

}

else {

int x = 1;

}

}

}

is permitted because the name x is never used in the outer block. end

example]

[Note: The rule of invariant meaning applies only to simple names. It is

perfectly valid for the same

identifier to have one meaning as a simple name and another meaning as

right operand of a member access

(?4.5.4). end note] [Example: For example:

struct Point

{

int x, y;

public Point(int x, int y) {

this.x = x;

this.y = y;

}

}

The example above illustrates a common pattern of using the names of fields

as parameter names in an

instance constructor. In the example, the simple names x and y refer to the

parameters, but that does not

prevent the member access expressions this.x and this.y from accessing the

fields. end example]

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有