nested class inheritance

Doesn't this make sense? class Fruit { class Seed { } } class Apple: Fruit { class AppleSeed: Fruit.Seed { } } This means, that as Fruit.Seed needs access to enclosing Fruit, AppleSeed, being a Fruit.Seed will also have access to enclosing Fruit, which is Apple. DMD 0.259 has this to sa

Re: nested class inheritance

On 7/13/12 1:59 PM, Gor Gyolchanyan wrote: Doesn't this make sense? class Fruit { class Seed { } } class Apple: Fruit { class AppleSeed: Fruit.Seed { } } This means, that as Fruit.Seed needs access to enclosing Fruit, AppleSeed, being a Fruit.Seed will also have access to enclosing

Re: nested class inheritance

On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: Doesn't this make sense? class Fruit { class Seed { } } class Apple: Fruit { class AppleSeed: Fruit.Seed { } } This means, that as Fruit.Seed needs access to enclosing Fruit, AppleSeed, being a Fruit.Seed will also have

Re: nested class inheritance

On Fri, Jul 13, 2012 at 10:19 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 1:59 PM, Gor Gyolchanyan wrote: > >> Doesn't this make sense? >> >> class Fruit >> { >> class Seed { } >> } >> >> class Apple: Fruit >> { >> class AppleSeed: Fruit.Seed { } >> } >>

Re: nested class inheritance

On Fri, Jul 13, 2012 at 10:25 PM, Era Scarecrow wrote: > On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: > >> Doesn't this make sense? >> >> class Fruit >> { >> class Seed { } >> } >> >> class Apple: Fruit >> { >> class AppleSeed: Fruit.Seed { } >> } >> >> This means, tha

Re: nested class inheritance

On Friday, 13 July 2012 at 18:34:06 UTC, Gor Gyolchanyan wrote: I need Seed to have a reference to Fruit because there will be more then one derivative of Seed in the same derivative of Fruit and they all need to store data inside the fruit and communicate with each other in that way. That's wh

Re: nested class inheritance

"Era Scarecrow" , dans le message (digitalmars.D:172269), a écrit : > class Fruit { > int x; > class Seed { >void oneMoreToX() { > x++; //knows about Fruit.x, even if not instantiated >} > } > > static class Seed2 { >void oneMoreToX() { > // x++; //fails to compile, no kno

Re: nested class inheritance

"Era Scarecrow" , dans le message (digitalmars.D:172272), a écrit : > Then perhaps have the inherited class within fruit? > > class Fruit { >class Seed {} >class Appleseed : Seed {} > } But then AppleSeed doesn't know about Apple

Re: nested class inheritance

On Fri, Jul 13, 2012 at 10:55 PM, Christophe Travert < trav...@phare.normalesup.org> wrote: > "Era Scarecrow" , dans le message (digitalmars.D:172272), a écrit : > > Then perhaps have the inherited class within fruit? > > > > class Fruit { > >class Seed {} > >class Appleseed : Seed {} >

Re: nested class inheritance

On Friday, 13 July 2012 at 18:55:28 UTC, trav...@phare.normalesup.org (Christophe Travert) wrote: "Era Scarecrow" , dans le message (digitalmars.D:172272), a écrit : Then perhaps have the inherited class within fruit? class Fruit { class Seed {} class Appleseed : Seed {} } But then Ap

Re: nested class inheritance

On 7/13/12 2:30 PM, Gor Gyolchanyan wrote: The whole point is to have it not static. I need it to be properly nested with the this.outer. What would be the type of this.outer? Andrei

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:03 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 2:30 PM, Gor Gyolchanyan wrote: > >> The whole point is to have it not static. I need it to be properly >> nested with the this.outer. >> > > What would be the type of this.outer? > > Andrei

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:02 PM, Era Scarecrow wrote: > On Friday, 13 July 2012 at 18:55:28 UTC, > trav...@phare.normalesup.org(Christophe Travert) wrote: > >> "Era Scarecrow" , dans le message (digitalmars.D:172272), a écrit : >> >>> Then perhaps have the inherited class within fruit? >>> >>

Re: nested class inheritance

On 7/13/12 3:07 PM, Gor Gyolchanyan wrote: On Fri, Jul 13, 2012 at 11:03 PM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.org>> wrote: On 7/13/12 2:30 PM, Gor Gyolchanyan wrote: The whole point is to have it not static. I need it to be properly nested with the this.o

Re: nested class inheritance

Andrei Alexandrescu , dans le message (digitalmars.D:172280), a écrit : >> For Fruit.Seed it's Fruit, for AppleSeed it's Apple. This makes sense >> because the Apple, which AppleSeed sees is the same object, which >> Fruit.Seed sees as it's base type Fruit. > > That would mean AppleSeed has two ou

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:10 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 3:07 PM, Gor Gyolchanyan wrote: > >> On Fri, Jul 13, 2012 at 11:03 PM, Andrei Alexandrescu >> > > >> >> >> wrote: >> >> On 7/13/12 2:30 PM, Gor Gy

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:18 PM, Christophe Travert < trav...@phare.normalesup.org> wrote: > Andrei Alexandrescu , dans le message (digitalmars.D:172280), a écrit : > >> For Fruit.Seed it's Fruit, for AppleSeed it's Apple. This makes sense > >> because the Apple, which AppleSeed sees is the same

Re: nested class inheritance

On Friday, 13 July 2012 at 19:08:54 UTC, Gor Gyolchanyan wrote: If you make seed static, then Appleseed & apple will have access to Fruit but seed (by itself) won't. Other combinations faile as far as I can tell. How far you can take inner class inheritance I don't know, but it seems not that

Re: nested class inheritance

On 7/13/12 3:18 PM, Christophe Travert wrote: Andrei Alexandrescu , dans le message (digitalmars.D:172280), a écrit : For Fruit.Seed it's Fruit, for AppleSeed it's Apple. This makes sense because the Apple, which AppleSeed sees is the same object, which Fruit.Seed sees as it's base type Fruit.

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:26 PM, Era Scarecrow wrote: > On Friday, 13 July 2012 at 19:08:54 UTC, Gor Gyolchanyan wrote: > > If you make seed static, then Appleseed & apple will have access to Fruit >>> but seed (by itself) won't. Other combinations faile as far as I can tell. >>> How far you ca

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:30 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 3:18 PM, Christophe Travert wrote: > >> Andrei Alexandrescu , dans le message (digitalmars.D:172280), a écrit : >> >>> For Fruit.Seed it's Fruit, for AppleSeed it's Apple. This makes sense >>

Re: nested class inheritance

On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: The initial question was: why does DMD 2.059 reject this if this makes sense? It's not even a new feature. It's a (possibly) new (and apparently sensible) use case of an existing feature. I think the simple answer is there was no provision for it. The

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:41 PM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: > >> The initial question was: why does DMD 2.059 reject this if this makes >> sense? >> It's not even a new feature. It's a (possibly) new (and apparently >>

Re: nested class inheritance

On Friday, 13 July 2012 at 19:35:34 UTC, Gor Gyolchanyan wrote: The seed can't be an interface because it needs to contain state. For instance the progress towards becoming the respective fruit. The interface itself may not have state, but what uses the interface can have state. So i don't

Re: nested class inheritance

On Fri, Jul 13, 2012 at 11:59 PM, Era Scarecrow wrote: > On Friday, 13 July 2012 at 19:35:34 UTC, Gor Gyolchanyan wrote: > >> >> The seed can't be an interface because it needs to contain state. For >> instance the progress towards becoming the respective fruit. >> > > The interface itself may n

Re: nested class inheritance

On 7/13/12 3:49 PM, Gor Gyolchanyan wrote: On Fri, Jul 13, 2012 at 11:41 PM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.org>> wrote: On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: The initial question was: why does DMD 2.059 reject this if this makes sense?

Re: nested class inheritance

On Fri, 13 Jul 2012 13:59:54 -0400, Gor Gyolchanyan wrote: Doesn't this make sense? class Fruit { class Seed { } } class Apple: Fruit { class AppleSeed: Fruit.Seed { } } This means, that as Fruit.Seed needs access to enclosing Fruit, AppleSeed, being a Fruit.Seed will also have

Re: nested class inheritance

On Friday, 13 July 2012 at 20:04:43 UTC, Gor Gyolchanyan wrote: On Fri, Jul 13, 2012 at 11:59 PM, Era Scarecrow or perhaps...? interface Seed{} interface Fruit{} //Apple knows it's a fruit.. class Apple : Fruit { //Appleseed is from the Apple (which is a fruit as well) //Appleseed is a see

Re: nested class inheritance

On Sat, Jul 14, 2012 at 12:31 AM, Andrei Alexandrescu < seewebsiteforem...@erdani.org> wrote: > On 7/13/12 3:49 PM, Gor Gyolchanyan wrote: > >> On Fri, Jul 13, 2012 at 11:41 PM, Andrei Alexandrescu >> > > >> >> >> wrote: >> >> On 7/13/12 3:36 PM, Gor Gy

Re: nested class inheritance

On 07/13/12 21:41, Andrei Alexandrescu wrote: > On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: >> The initial question was: why does DMD 2.059 reject this if this makes >> sense? >> It's not even a new feature. It's a (possibly) new (and apparently >> sensible) use case of an existing feature. > > I t

Re: nested class inheritance

On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: Which doesn't make sense, IMO. What do you guys think about this? Who makes more sense me or DMD 2.059? http://d.puremagic.com/issues/show_bug.cgi?id=1175 https://github.com/D-Programming-Language/dmd/pull/889

Re: nested class inheritance

On Sat, Jul 14, 2012 at 1:36 PM, Guillaume Chatelet < chatelet.guilla...@gmail.com> wrote: > On 07/13/12 21:41, Andrei Alexandrescu wrote: > > On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: > >> The initial question was: why does DMD 2.059 reject this if this makes > >> sense? > >> It's not even a new

Re: nested class inheritance

On Sat, Jul 14, 2012 at 1:41 PM, Vladimir Panteleev < vladi...@thecybershadow.net> wrote: > On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: > >> Which doesn't make sense, IMO. What do you guys think about this? Who >> makes >> more sense me or DMD 2.059? >> > > http://d.puremagic.c

Re: nested class inheritance

On Saturday, July 14, 2012 13:47:29 Gor Gyolchanyan wrote: > I see it's already merged. I presume this will end up in DMD 2.060, right? Anything and everything which has already been merged on github will end up in the next release of dmd unless it's reverted or altered by another commit prior t

Re: nested class inheritance

On Sat, Jul 14, 2012 at 1:56 PM, Jonathan M Davis wrote: > On Saturday, July 14, 2012 13:47:29 Gor Gyolchanyan wrote: > > I see it's already merged. I presume this will end up in DMD 2.060, > right? > > Anything and everything which has already been merged on github will end > up in > the next rel

Re: nested class inheritance

On Saturday, July 14, 2012 14:00:14 Gor Gyolchanyan wrote: > That's great. That means, I don't have to work around it and I can just > wait a bit until DMD 2.060 comes out. Btw, when will it happen? No idea. Normally, releases have been happening every 2 months or so, but we're at just passed 3 m

Re: nested class inheritance

On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis wrote: > On Saturday, July 14, 2012 14:00:14 Gor Gyolchanyan wrote: > > That's great. That means, I don't have to work around it and I can just > > wait a bit until DMD 2.060 comes out. Btw, when will it happen? > > No idea. Normally, releases have

Re: nested class inheritance

On Saturday, July 14, 2012 14:21:01 Gor Gyolchanyan wrote: > On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis wrote: > > On Saturday, July 14, 2012 14:00:14 Gor Gyolchanyan wrote: > > > That's great. That means, I don't have to work around it and I can just > > > wait a bit until DMD 2.060 comes

Re: nested class inheritance

On Sat, Jul 14, 2012 at 2:35 PM, Jonathan M Davis wrote: > On Saturday, July 14, 2012 14:21:01 Gor Gyolchanyan wrote: > > On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis > wrote: > > > On Saturday, July 14, 2012 14:00:14 Gor Gyolchanyan wrote: > > > > That's great. That means, I don't have to wo

Re: nested class inheritance

Am 14.07.2012 11:45, schrieb Gor Gyolchanyan: On Sat, Jul 14, 2012 at 1:36 PM, Guillaume Chatelet mailto:chatelet.guilla...@gmail.com>> wrote: On 07/13/12 21:41, Andrei Alexandrescu wrote: > On 7/13/12 3:36 PM, Gor Gyolchanyan wrote: >> The initial question was: why does DMD 2.059

Re: nested class inheritance

On 7/14/12 5:36 AM, Guillaume Chatelet wrote: class Fruit { class Seed { } } class Apple extends Fruit { class AppleSeed extends Fruit.Seed { Apple getOuter() { return Apple.this; } } } class Main { public static void main(String[] args) {

Re: nested class inheritance

On 07/14/12 13:51, Andrei Alexandrescu wrote: > On 7/14/12 5:36 AM, Guillaume Chatelet wrote: >> class Fruit { >> class Seed { >> } >> } >> >> class Apple extends Fruit { >> class AppleSeed extends Fruit.Seed { >> Apple getOuter() { >> return Apple.this; >>

Re: nested class inheritance

On 07/14/12 11:41, Vladimir Panteleev wrote: > On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: >> Which doesn't make sense, IMO. What do you guys think about this? Who >> makes >> more sense me or DMD 2.059? > > http://d.puremagic.com/issues/show_bug.cgi?id=1175 > https://github.co

Re: nested class inheritance

On Sat, Jul 14, 2012 at 4:17 PM, Guillaume Chatelet < chatelet.guilla...@gmail.com> wrote: > On 07/14/12 11:41, Vladimir Panteleev wrote: > > On Friday, 13 July 2012 at 18:00:05 UTC, Gor Gyolchanyan wrote: > >> Which doesn't make sense, IMO. What do you guys think about this? Who > >> makes > >> m

Re: nested class inheritance

On 13/07/2012 21:10, Andrei Alexandrescu wrote: On 7/13/12 3:07 PM, Gor Gyolchanyan wrote: On Fri, Jul 13, 2012 at 11:03 PM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.org>> wrote: On 7/13/12 2:30 PM, Gor Gyolchanyan wrote: The whole point is to have it not static. I need it to be pr

Re: nested class inheritance

On 14/07/2012 08:27, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 12:31 AM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.org>> wrote: On 7/13/12 3:49 PM, Gor Gyolchanyan wrote: On Fri, Jul 13, 2012 at 11:41 PM, Andrei Alexandrescu mailto:seewebsiteforem...@erdani.o

Re: nested class inheritance

On Sat, Jul 14, 2012 at 8:17 PM, deadalnix wrote: > On 14/07/2012 08:27, Gor Gyolchanyan wrote: > >> On Sat, Jul 14, 2012 at 12:31 AM, Andrei Alexandrescu >> >> > > >> >> wrote: >> >> On 7/13/12 3:49 PM, Gor Gyolchanyan wrote: >> >> On Fri, Jul

Re: nested class inheritance

The only problem about this is: class Fruit { class Seed { void SetFruit(Fruit fruit) { this.outer = fruit; } } } class Apple: Fruit { void AppleOnlyMethod(){ ... } class AppleSeed: Fruit.Seed { void DoSomething() { AppleOnlyMethod(); } } auto Ge

Re: nested class inheritance

On Sat, Jul 14, 2012 at 9:12 PM, Benjamin Thaut wrote: > The only problem about this is: > > class Fruit > { > class Seed { > void SetFruit(Fruit fruit) > { > this.outer = fruit; > } > } > } > > class Apple: Fruit > { > void AppleOnlyMethod(){ ... } > > class AppleSeed: F

Re: nested class inheritance

2012/7/15 Benjamin Thaut : > The only problem about this is: > > class Fruit > { > class Seed { > void SetFruit(Fruit fruit) > { > this.outer = fruit; Setting to pseudo variable 'outer' should be rejected in compilation. Please report it to bugzilla. > } > } > } > > class Ap

Re: nested class inheritance

Am 14.07.2012 19:21, schrieb kenji hara: 2012/7/15 Benjamin Thaut : The only problem about this is: class Fruit { class Seed { void SetFruit(Fruit fruit) { this.outer = fruit; Setting to pseudo variable 'outer' should be rejected in compilation. Please report it to bugzill

Re: nested class inheritance

Am 14.07.2012 19:18, schrieb Gor Gyolchanyan: On Sat, Jul 14, 2012 at 9:12 PM, Benjamin Thaut mailto:c...@benjamin-thaut.de>> wrote: The only problem about this is: class Fruit { class Seed { void SetFruit(Fruit fruit) { this.outer = fruit;

Re: nested class inheritance

On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut wrote: > Am 14.07.2012 19:21, schrieb kenji hara: > >> 2012/7/15 Benjamin Thaut : >> >> The only problem about this is: >>> >>> class Fruit >>> { >>>class Seed { >>> void SetFruit(Fruit fruit) >>> { >>>this.outer = fruit; >>> >

Re: nested class inheritance

Am 14.07.2012 19:30, schrieb Gor Gyolchanyan: On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut mailto:c...@benjamin-thaut.de>> wrote: Am 14.07.2012 19:21, schrieb kenji hara: 2012/7/15 Benjamin Thaut mailto:c...@benjamin-thaut.de>>: The only problem about this is:

Re: nested class inheritance

On 07/15/2012 12:55 AM, Benjamin Thaut wrote: Am 14.07.2012 19:30, schrieb Gor Gyolchanyan: On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut mailto:c...@benjamin-thaut.de>> wrote: Am 14.07.2012 19:21, schrieb kenji hara: 2012/7/15 Benjamin Thaut mailto:c...@benjamin-thaut.de>>: The only proble

Re: nested class inheritance

Am 15.07.2012 02:02, schrieb Timon Gehr: On 07/15/2012 12:55 AM, Benjamin Thaut wrote: Am 14.07.2012 19:30, schrieb Gor Gyolchanyan: On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut mailto:c...@benjamin-thaut.de>> wrote: Am 14.07.2012 19:21, schrieb kenji hara: 2012/7/15 Benjamin Thaut mailto:

Re: nested class inheritance

On Sun, Jul 15, 2012 at 1:41 PM, Benjamin Thaut wrote: > Am 15.07.2012 02:02, schrieb Timon Gehr: > > On 07/15/2012 12:55 AM, Benjamin Thaut wrote: >> >>> Am 14.07.2012 19:30, schrieb Gor Gyolchanyan: >>> On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut >>> >

Re: nested class inheritance

On Sun, Jul 15, 2012 at 1:41 PM, Benjamin Thaut wrote: > Am 15.07.2012 02:02, schrieb Timon Gehr: > > On 07/15/2012 12:55 AM, Benjamin Thaut wrote: >> >>> Am 14.07.2012 19:30, schrieb Gor Gyolchanyan: >>> On Sat, Jul 14, 2012 at 9:23 PM, Benjamin Thaut >>> >

Re: nested class inheritance

Am 15.07.2012 13:24, schrieb Gor Gyolchanyan: On Sun, Jul 15, 2012 at 1:41 PM, Benjamin Thaut mailto:c...@benjamin-thaut.de>> wrote: Am 15.07.2012 02:02, schrieb Timon Gehr: On 07/15/2012 12:55 AM, Benjamin Thaut wrote: Am 14.07.2012 19:30, schrieb Gor Gyolchanyan:

Re: nested class inheritance

On Sun, Jul 15, 2012 at 3:35 PM, Benjamin Thaut wrote: > Am 15.07.2012 13:24, schrieb Gor Gyolchanyan: > >> On Sun, Jul 15, 2012 at 1:41 PM, Benjamin Thaut > >> > wrote: >> >> Am 15.07.2012 02:02, schrieb Timon Gehr: >> >> On 07/15/2012 12:55 AM, Benjam