[#BOO-724] Private fields conflict with same named fields in child class

Boo

Created: 19/Apr/06 03:39 PM Updated: 30/May/07 09:55 AM

Component/s:

Compiler

Affects Version/s:

0.7.5

Fix Version/s:

0.7.8

Time Tracking:

Not Specified

File Attachments:	1. BOO-724-v3.patch (3 kb)
Environment:	Windows XP Pro SP2, SharpDevelop 2.0.0.1291

Description

« Hide

[snip]
class Foo:
private _x as object

class Bar(Foo):
private _x as string

def constructor():
_x = "foo"
[/snip]

This code causes the compiler to complain "Expression cannot be assigned to" on the _x = "foo" line.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

This also causes this problem (from Socrates877 on the mailing list):

class A:
private _field as int

class B(A):
private _field as string

def Explosion():
print(_field)

Ambiguous reference '_field': Data.B._field, Data.A._field. (BCE0004)

[ Permlink | « Hide ]

Patch to strip inaccessible references during ProcessMethodModies during ambiguity resolution.

[ Permlink | « Hide ]

On second thoughts, should we use ResolveAmbiguousReferenceByAccessibility before doing anything else? That might fix e.g. BOO-477

[ Permlink | « Hide ]

At Avishs suggestion added a test case for protected, internal, public...

[ Permlink | « Hide ]

Someone review this patch yet?

[ Permlink | « Hide ]

I'm taking care of it.

[ Permlink | « Hide ]

Patch applied. Thanks!