incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joan Llenas Masó <joan.llenas.m...@gmail.com>
Subject Re: Namespaces in Interfaces, AVM or Compiler Problem
Date Mon, 16 Jan 2012 12:24:03 GMT
mmm, namespaces in interfaces would be a cheap solution to method
overloading.

v1 function doThis();
v2 function doThis();

Ugly though...




--
Joan Llenas Masó
http://joan.garnet.io
@joangarnet (es)
@joanllenas (en)



On Mon, Jan 16, 2012 at 13:19, Martin Heidegger <mh@leichtgewicht.at> wrote:

> Interfaces describe the public access to a class. The "private" or
> "protected" namespace are security mechanisms that actually limit the
> access for foreign objects.
> All properties of a class with a namespace are in fact accessible public,
> just the way to address them is different.
> Thus it should be possible for a interface to describe all public
> properties/methods even if you need a namespace to address them.
>
> yours
> Martin.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message