July 14, 2012
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

July 14, 2012
On Sat, Jul 14, 2012 at 1:36 PM, Guillaume Chatelet < chatelet.guillaume@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 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 feature copies the Java feature, and I don't think Java has something like what you defined.
> >
> > Andrei
> >
>
> 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) {
>         final Apple apple = new Apple();
>         final Apple.AppleSeed appleSeed = apple.new AppleSeed();
>         assert (appleSeed instanceof Fruit.Seed);
>         assert (apple == appleSeed.getOuter());
>         assert (appleSeed.getOuter() instanceof Apple);
>         assert (appleSeed.getOuter() instanceof Fruit);
>     }
> }
>
> This is valid Java code actually and I agree with Gor I would have expected it to work with D.
>
> Guillaume
>

I didn't even know this worked in Java. This means, that nested classed in D can't translate nested classed in Java after all.

-- 
Bye,
Gor Gyolchanyan.


July 14, 2012
On Sat, Jul 14, 2012 at 1:41 PM, Vladimir Panteleev < vladimir@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.com/issues/**show_bug.cgi?id=1175<http://d.puremagic.com/issues/show_bug.cgi?id=1175> https://github.com/D-**Programming-Language/dmd/pull/**889<https://github.com/D-Programming-Language/dmd/pull/889>
>
>
I see it's already merged. I presume this will end up in DMD 2.060, right?

-- 
Bye,
Gor Gyolchanyan.


July 14, 2012
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 to the next release. We don't currently maintain any branches as part of the development process.

- Jonathan M Davis
July 14, 2012
On Sat, Jul 14, 2012 at 1:56 PM, Jonathan M Davis <jmdavisProg@gmx.com>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 release of dmd unless it's reverted or altered by another commit
> prior to the next release. We don't currently maintain any branches as
> part of
> the development process.
>
> - Jonathan M Davis
>

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?

-- 
Bye,
Gor Gyolchanyan.


July 14, 2012
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 months since the last one now. It pretty much depends on when Walter decides to do a beta. He made noise about that over a month ago but didn't end up doing it (I think that he went on vacation shortly after that), and he hasn't said anything about it since. We should probably do one soon though.

- Jonathan M Davis
July 14, 2012
On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis <jmdavisProg@gmx.com>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 been happening every 2 months or so, but
> we're at just passed 3 months since the last one now. It pretty much
> depends
> on when Walter decides to do a beta. He made noise about that over a month
> ago
> but didn't end up doing it (I think that he went on vacation shortly after
> that), and he hasn't said anything about it since. We should probably do
> one
> soon though.
>
> - Jonathan M Davis
>

I see. Is it possible to get the change log for the upcoming release? That would also show us what we shouldn't work around.

-- 
Bye,
Gor Gyolchanyan.


July 14, 2012
On Saturday, July 14, 2012 14:21:01 Gor Gyolchanyan wrote:
> On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis
<jmdavisProg@gmx.com>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 been happening every 2 months or so, but
> > we're at just passed 3 months since the last one now. It pretty much
> > depends
> > on when Walter decides to do a beta. He made noise about that over a month
> > ago
> > but didn't end up doing it (I think that he went on vacation shortly after
> > that), and he hasn't said anything about it since. We should probably do
> > one
> > soon though.
> > 
> > - Jonathan M Davis
> 
> I see. Is it possible to get the change log for the upcoming release? That would also show us what we shouldn't work around.

Yes and no. If you look in each repository, there's a partial changelog for each (changelog.dd), but odds are that they're missing a number of items, and actually, for some reason, dmd's hasn't been updated in a year, so I have no clue how Walter puts together dmd's portion of the changelog.

Andrei recently brought up the idea of automatically generating the bug fix list for the changelog with a query to bugzilla, which would make sure that everything made it into the changelog (right now, it depends on the devs making sure that they manually add it all, and stuff gets missed). I believe that this query will list every bug that has been fixed since 2.059:

http://d.puremagic.com/issues/buglist.cgi?bug_status=RESOLVED&chfieldto=Now&chfield=bug_status&query_format=advanced&chfieldfrom=2012-04-12&resolution=FIXED

which as you can see is far from being short.

- Jonathan M Davis
July 14, 2012
On Sat, Jul 14, 2012 at 2:35 PM, Jonathan M Davis <jmdavisProg@gmx.com>wrote:

> On Saturday, July 14, 2012 14:21:01 Gor Gyolchanyan wrote:
> > On Sat, Jul 14, 2012 at 2:04 PM, Jonathan M Davis
> <jmdavisProg@gmx.com>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 been happening every 2 months or so,
> but
> > > we're at just passed 3 months since the last one now. It pretty much
> > > depends
> > > on when Walter decides to do a beta. He made noise about that over a
> month
> > > ago
> > > but didn't end up doing it (I think that he went on vacation shortly
> after
> > > that), and he hasn't said anything about it since. We should probably
> do
> > > one
> > > soon though.
> > >
> > > - Jonathan M Davis
> >
> > I see. Is it possible to get the change log for the upcoming release?
> That
> > would also show us what we shouldn't work around.
>
> Yes and no. If you look in each repository, there's a partial changelog for
> each (changelog.dd), but odds are that they're missing a number of items,
> and
> actually, for some reason, dmd's hasn't been updated in a year, so I have
> no
> clue how Walter puts together dmd's portion of the changelog.
>
> Andrei recently brought up the idea of automatically generating the bug fix
> list for the changelog with a query to bugzilla, which would make sure that
> everything made it into the changelog (right now, it depends on the devs
> making sure that they manually add it all, and stuff gets missed). I
> believe
> that this query will list every bug that has been fixed since 2.059:
>
>
> http://d.puremagic.com/issues/buglist.cgi?bug_status=RESOLVED&chfieldto=Now&chfield=bug_status&query_format=advanced&chfieldfrom=2012-04-12&resolution=FIXED
>
> which as you can see is far from being short.
>
> - Jonathan M Davis
>

Auto-generating a change log is a great idea. I think it would be great to generate the change log for all previous versions as well and diff it with the existing change log to see the changes that didn't show up in the change log.

-- 
Bye,
Gor Gyolchanyan.


July 14, 2012
Am 14.07.2012 11:45, schrieb Gor Gyolchanyan:
> On Sat, Jul 14, 2012 at 1:36 PM, Guillaume Chatelet
> <chatelet.guillaume@gmail.com <mailto:chatelet.guillaume@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 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
>     feature
>      > copies the Java feature, and I don't think Java has something
>     like what
>      > you defined.
>      >
>      > Andrei
>      >
>
>     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) {
>              final Apple apple = new Apple();
>              final Apple.AppleSeed appleSeed = apple.new AppleSeed();
>              assert (appleSeed instanceof Fruit.Seed);
>              assert (apple == appleSeed.getOuter());
>              assert (appleSeed.getOuter() instanceof Apple);
>              assert (appleSeed.getOuter() instanceof Fruit);
>          }
>     }
>
>     This is valid Java code actually and I agree with Gor I would have
>     expected it to work with D.
>
>     Guillaume
>
>
> I didn't even know this worked in Java. This means, that nested classed
> in D can't translate nested classed in Java after all.
>

This usually comes up in certification and interview questions.