Btw. what is the best way to add a comment question?

For instance about the nested functions example:

Why not exclude the lines:
bit found;
while (!found), and
found=true;

They don't seem to add anything except complexity.

== Quote from Saaa (empty@needmail.com)'s article
> >> Maybe see D1 and D2 seperated?
> >
> > Is there any D2 code in there?
> I mean for the future :)

Yes, in the future, I would expect there to be D2 code in the tutorials.

But I don't know how stable D2 is now (I know that Walter is planning to add stuff, but I don't know how many breaking changes are planned). If someone else wants to start adding D2 code, I won't get in the way, but I've personally been waiting until it stabilizes. I guess the const stuff may be mostly staying the way that it is now, but I get tired of chasing a moving target. I've been sticking to D1 with my D projects.

D2 is very much the frontier right now. Tango isn't available for D2 yet (I think I heard they're working on it behind the scenes). I haven't heard that DFL or DWT are supporting D2 yet. I don't think that D2 is for the faint of heart, and I'd recommend for newbies to concentrate on learning D1 at this point.

== Quote from Saaa (empty@needmail.com)'s article
> Btw. what is the best way to add a comment question?

Maybe just add a section to the wiki page. For example:

== Comment ==

Why not exclude the lines:
{{{
#!d
bit found;
while (!found), and
found=true;
}}}

They don't seem to add anything except complexity.
--Saaa


> For instance about the nested functions example:
> Why not exclude the lines:
> bit found;
> while (!found), and
> found=true;
> They don't seem to add anything except complexity.

To answer the question that you wanted to comment on, I'm not sure, but I think it was just my personal preference when I posted that code in 2004.

Example code can be too complicated or too short. If it's too complicated, someone may not understand the code. If it's too simple the point of the example might be lost. The "perfect balance" between the two extremes will vary from person to person. Perhaps this example is more complicated that it should be. I suspect that I was trying to show how useful a nested function could be.

It doesn't seem that complex to me, but perhaps that's because I've been programming too long. ;)

== Quote from Saaa (empty@needmail.com)'s article
...
> > I looked into creating some examples that would work for Phobos and Tango (using version(Tango)), but it was harder to do than I thought it would be, so I don't think I ever added any pages based on my efforts.
> Maybe adding one of your efforts? and explaining why it doesn't work exactly like you would like.

Well, since Tango downloads are available that include Tangobos now, it might be less of an issue than it was before. If people want "pure Tango" examples they can find them in the Tango wiki. If people don't mind using Tangobos, most of the tutorials should run without any modification needed. (I guess I might install a recent version of Tango to see if this is true.)

Maybe its even more complex than I thought, but my problem with the extra code would be that the while loop isn't really used: There is no loop :)

> == Quote from Saaa (empty@needmail.com)'s article
>> Btw. what is the best way to add a comment question?
>
> Maybe just add a section to the wiki page. For example:
>
> == Comment ==
>
> Why not exclude the lines:
> {{{
> #!d
> bit found;
> while (!found), and
> found=true;
> }}}
>
> They don't seem to add anything except complexity.
> --Saaa
>
>
>> For instance about the nested functions example:
>> Why not exclude the lines:
>> bit found;
>> while (!found), and
>> found=true;
>> They don't seem to add anything except complexity.
>
> To answer the question that you wanted to comment on, I'm not sure, but I
> think it
> was just my personal preference when I posted that code in 2004.
>
> Example code can be too complicated or too short. If it's too complicated,
> someone
> may not understand the code. If it's too simple the point of the example
> might be
> lost. The "perfect balance" between the two extremes will vary from person
> to
> person. Perhaps this example is more complicated that it should be. I
> suspect that
> I was trying to show how useful a nested function could be.
>
> It doesn't seem that complex to me, but perhaps that's because I've been programming too long. ;)