I don't think I can even once claim to have used a programming language that was so well documented that 75% of all the information you would ever need could be found in it's documentation.
I'm sure, but I didn't say all the information I would ever need, did I? I said all the information I've needed in the first week of learning. In other words, the most basic new features.
For as long as I've been programming (20+ years), personal improvement has always been a case of sharing your experiences with your friends and co-workers, and listening to their experiences. Reading books account for roughly 15% of what you can learn about programming. The other 85% you have to learn by actually programming.
No argument, but in the first week of playing with it, and to be honest, it's been no more than an hour here and there, so a week makes it sound a lot more impressive than it really is, I've got nowhere near to touching the 85% you learn by programming. I'm just trying to pick up the very basic stuff, and so far I'm doing most of that using your samples, the module source and these forums.
I think it's a bit harsh to go trawling through modules and expect the internals (like list.addlast) to be documented. Don't get me wrong, it's nice stuff to know, but it's not a neccessity, and i think it would just confuse the issue for people with less experience.
Well none of the new stuff is a necessity, I suppose, but yes, I do think that the important internals ( List.AddLast is a good example ) need some documentation. Heck, at the very least, a list of the internals, sorted into fields, methods and functions. Even if there was no explanation, it would be some help to be able to double F1 on TList and see a list of the internals. I dread to think what people with less experience will make of the docs.