15 messages in net.java.dev.openjfx-compiler.devRe: accessibility proposal
FromSent OnAttachments
Per BothnerJun 16, 2008 4:21 pm 
Robert FieldJun 16, 2008 9:48 pm 
Joshua SmithJun 16, 2008 10:24 pm 
Rémi ForaxJun 17, 2008 12:57 am 
Ethan NicholasJun 18, 2008 6:40 am 
Brian GoetzJun 18, 2008 7:37 am 
Shannon HickeyJun 18, 2008 7:44 am 
Brian GoetzJun 18, 2008 8:05 am 
Robert FieldJun 18, 2008 9:32 am 
Per BothnerJun 18, 2008 12:16 pm 
Dean IversonJun 18, 2008 12:51 pm 
Brian GoetzJun 18, 2008 12:56 pm 
Dean IversonJun 18, 2008 1:22 pm 
Brian GoetzJun 18, 2008 1:26 pm 
Christopher OliverJun 18, 2008 2:09 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: accessibility proposalActions...
From:Per Bothner (Per.@Sun.COM)
Date:Jun 18, 2008 12:16:33 pm
List:net.java.dev.openjfx-compiler.dev

Rémi Forax wrote:

Per Bothner a écrit :

If class A has an attribute m, and B extends A, what happens if B also declares m? Do these clash, or is A.m "hidden" from B? In Java a field A.m is hidden from B if and only if m is declared as private - overwise (correct me if I'm wrong...)

you're wrong :) see section 8.3.3.2 of JLS3. field hidding is not related to accessibility modifiers (private, etc).

Ah, yes.

And we can presumably use the "named super" mechanism to access hidden but accessible fields:

class A { attribute x : Integer; } class B extends A { attribute x : Number = A.x; }

Here the A.x refers to the x field in A.

-- --Per Bothner per.@sun.com pe@bothner.com http://per.bothner.com/

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-@openjfx-compiler.dev.java.net For additional commands, e-mail: dev-@openjfx-compiler.dev.java.net