> I don't think there is a trouble in creating them, but maintaining them.
>
> ~ Clay

When they are greatly outdated I'll post a call to update them again, ok?

If you would create one, I'll be happy =)

D1 would probably stay pretty updated as long as the std part isn't too big.

== Quote from okibi (spam@ratedo.com)'s article
...
> I used to read over the code at dsource, but it's terribly out of date. I pretty much just read over either the specs here or go to docwiki.net and figure it out. If the brain fart is too massive, I post here.
>
> I don't think there's any really good place for up to date d examples  yet. Maybe we should put some work into the dsource tutorials?

By the way, anyone should free to login and fix any of the dsource tutorials that have problems. Even someone doesn't want to directly "fix" the problem (perhaps it would take too much time or the solution isn't known), just adding a comment that there's a problem can be help give a clue to someone else that there's a problem that needs fixing.

== Quote from Saaa (empty@needmail.com)'s article
> >
> > I guess you're thinking of a different kind of tutorials than me, then. I'd think at least you'd need writefln/Stdout at some point in your tutorials.  I would think how to use writefln/Stdout would even be the subject of one of the first few tutorials.
> >
> > --bb
>
> I would suggest using phobos by default as it is the standard library and adding tango to the category if  it is used instead.

Since the tutorials project began before the Tango project began, there's already an established pro-Phobos bias. ;)

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.


> Anybody starting off would see phobos as the std.
> (I did :) and still do btw. whether tango is better or not.

I'm not against people adding Tango examples to the Tutorials project, but they should include a mention of Tango (something like "Tango is required").

It's helpful to mention which combination of compiler version/library version it's been tested with so that if breaks, future users will have a clue as to why it broke.

== Quote from Bill Baxter (dnewsgroup@billbaxter.com)'s article
> Saaa wrote:
> >> Saaa wrote:
> >>> With all the different design possibilities of D I find looking through code (from others) especially useful.
> >>>
> >>> The first place I always go to is dsource tutorials and thus
> >>> love to see it expanded.
> >>> Maybe see D1 and D2 seperated?
> >> Maybe D1|Phobos, D1|Tango, D2, actually.
> >>
> >> --bb
> >
> > I thought to include that distinction into the category.
> > Most tutorials are relatively small and don't necessarily need any
> > std lib.
>
> I guess you're thinking of a different kind of tutorials than me, then.
>
>    I'd think at least you'd need writefln/Stdout at some point in
> your tutorials.  I would think how to use writefln/Stdout would even
> be the subject of one of the first few tutorials.
>
> --bb

I agree. Newcomers who want to use the Tutorials with Tango should probably install the Tango that comes with Tangobos.

== Quote from Saaa (empty@needmail.com)'s article
> How about forcing =) everybody on the newsgroup creating one tutorial?
> (I mean 1 per person would be quit a bit of code)

That's fine with me since I already submitted more than my quota a few years ago. ;)

== Quote from Bill Baxter (dnewsgroup@billbaxter.com)'s article
> Saaa wrote:
> > With all the different design possibilities of D I find looking through code (from others) especially useful.
> >
> > The first place I always go to is dsource tutorials and thus love
> > to see it expanded.
> > Maybe see D1 and D2 seperated?
>
> Maybe D1|Phobos, D1|Tango, D2, actually.
>
> --bb

Actually, I don't know if there's any D2 or Tango code in there (though I suppose some of "less useful" examples would comply in any situation), but you're right it'd be better if the compiler versions and needed libraries were indicated for every example.

I've added some of that compiler/library version information to older entries (and I try to include that information with new entries), but I confess it's not something that I really enjoy doing. Everyone is welcome to help improve the wiki pages. (Any registered dsource user should be able to edit the Tutorial wiki.)

> By the way, anyone should free to login and fix any of the dsource
> tutorials that
> have problems. Even someone doesn't want to directly "fix" the problem
> (perhaps it
> would take too much time or the solution isn't known), just adding a
> comment that
> there's a problem can be help give a clue to someone else that there's a
> problem
> that needs fixing.

agreed

> Since the tutorials project began before the Tango project began, there's
> already
> an established pro-Phobos bias. ;)
I'm not that ancient ;)

>
> 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.

>
>
>> Anybody starting off would see phobos as the std.
>> (I did :) and still do btw. whether tango is better or not.
>
> I'm not against people adding Tango examples to the Tutorials project, but
> they
> should include a mention of Tango (something like "Tango is required").
That's what I meant with the category. Or this could be included in the keywords.

> It's helpful to mention which combination of compiler version/library
> version it's
> been tested with so that if breaks, future users will have a clue as to
> why it broke.
agreed.

 (Any registered dsource user should be able to edit the Tutorial wiki.)

Didn't know that. I'll see if I can fabricate something interesting.

>> Maybe see D1 and D2 seperated?
>
> Is there any D2 code in there?

I mean for the future :)