Re: lazy vals and public bitmap$n field

IMHO it would be an important step towards Scala world leadership, if Scala could be used for CDI, because chances are that CDI will be widely adopted in the next couple of years. If you just somehow could make it ...

Heiko

On 22 November 2010 18:47, martin odersky <martin.odersky@epfl.ch> wrote:

-- 

Heiko Seeberger

On Mon, Nov 22, 2010 at 6:29 PM, Paul Phillips <paulp@improving.org> wrote:

On Mon, Nov 22, 2010 at 06:17:53PM +0100, iulian dragos wrote:

> OTOH I don't know if there's any real reason for having them public,

> other than Scala generally having troubles keeping access modifiers in

> check. They're for sure protected in the compiler's mind, so maybe the

> backed could do a better job at emitting them as such (we don't go

> through getters/setters for synthetics, like bitmap fields).

Last I checked (which was like a week ago) scala never emits protected

fields, only private or public.

 if (isConsideredPrivate) ACC_PRIVATE else ACC_PUBLIC,

I'm sure it will be tedious dicey work trying to make it more granular.

Why can't we just emity ACC_PROTECTED for protected access?

Cheers

 -- Martin 

Company: weiglewilczek.com

Blog: heikoseeberger.name

Follow me: twitter.com/hseeberger

OSGi on Scala: scalamodules.org

Lift, the simply functional web framework: liftweb.net
Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org