Hi ToddAndMargo, Thanks for the effort to improve the Raku docs. However, this is a Raku not OO (Object Oriented <https://en.wikipedia.org/wiki/Object-oriented_programming>) related tutorial. As JJ already pointed out, these pages are to show the reader how you get things done in Raku, not what OO or other programming concepts are. There are probably thousands of OO books around and can teach you what a class is and why you need them. See the Wikipedia link I linked above for example. That's not in the scope of this tutorial.
The parts you are missing are already there, but unfortunately not linked. You can find them in the Raku documentation: => <https://docs.raku.org/language/operators#infix_=%3E>, $! <https://docs.raku.org/language/variables#The_!_twigil> and $. <https://docs.raku.org/language/variables#The_._twigil> :$ stands for a named parameter <https://docs.raku.org/type/Signature#Positional_vs._named_arguments> and can be also found in the documentation. ^$ is used for ranges <https://docs.raku.org/type/Range>and is also already there. So the information you are missing is already there. You could argue that the links are missing and I would agree with you. But again this tutorial is for Raku classes not OO concept, Pairs, named parameters or ranges. I hope that helped, Wolfgang On Tue, 15 Dec 2020 at 05:28, ToddAndMargo via perl6-users < perl6-users@perl.org> wrote: > On 12/14/20 5:24 PM, Aureliano Guedes wrote: > > That's why, as a community-developed language (including docs) I'd like > > to suggest to you help to improve the docs. > > This way, when I have - with some lucky - free time, I may learn with > > you and all others that wrote these docs. > > Hi Aureliano, > > I absolutely adore Raku. But the docs are truly awful. > They do not start out simple and build to the complex. > They throw terms out without defining them. They use > things in examples that are require advanced level of > knowledge to understand, and so on and so forth. > They have broken virtually rule of technical writing. > The docs are simply refreshers for those that already > know what they are doing and do not need them. > > I have tried several times to contribute to and get > the docs improved. I have been told I am providing > too much detail or just get ignored. So I have > stopped. The culture of the "docs" is not something > I can change. > > I would absolute love to see some kind of contributed > docs portal that any user could pick out a subject and > write on it with the ability for others to correct > mistakes or add content. > > Once I get Classes and Object figured out, I will > write my own documentation of the subject. If I > think it is good enough to share (some of my technical > writing stinks too), I will post it back here. > > For starters, I need to have the definition of > "class" and "object". Then I need their rules. > > -T >
