5
5
6
6
7
7
* [ goals] ( #goals ) and [ methods] ( #teaching-method )
8
- * [ chapter layout] ( #chapter-layout )
9
8
* [ what app to build] ( #what-app-to-build )
9
+ * [ chapter layout] ( #chapter-layout )
10
10
* [ prerequisites] ( #prerequisites )
11
11
* [ Perl philosophy] ( #perl-philosophy )
12
12
* [ basic syntax rules] ( #basic-syntax-rules )
@@ -21,10 +21,10 @@ Welcome,
21
21
to this hands on tour through the more often needed parts of this vast and
22
22
beautiful programming language. You can find here:
23
23
24
- - syntax knowledge:
25
- - bits of deeper understanding for the design decisions:
26
- - room for own experiments:
27
- - a hopefully useful application:
24
+ - syntax knowledge
25
+ - bits of deeper understanding for the design decisions
26
+ - room for own experiments
27
+ - a hopefully useful application
28
28
- a taste of the full capabilities of Perl 6
29
29
- sources for further learning (docs and more)
30
30
@@ -52,47 +52,52 @@ favorite learning style. Rereading a chapter after that also clarifies a lot.
52
52
When an explanation still doesn't makes sense to you - please let us know via github.
53
53
54
54
The flip side of this practical, yet dense approach: you (mostly) have to stick
55
- with the given order and won't be able to skip even several sentences.
56
- Because then you overlook the introduction of an important feature, which will be
57
- premised over and over. This is especially true during chapter 2-6 and an inevitable
55
+ with the given order and won't be able to skip even several sentences without
56
+ risking to miss the introduction of an important feature, which will be premised
57
+ over and over. This is especially true during chapter 2-6 and an inevitable
58
58
side effect of developing one example program throughout the whole tutorial.
59
59
While we strongly recommend to adapt it to your wishes, you should be be aware,
60
- that maintaining them through all changes can be a demanding task.
60
+ that maintaining your modifications through the chapter can be a demanding task.
61
+
62
+
63
+
64
+ [ What App To Build] ( #chapter-0 )
65
+ -------------------------------
66
+ What program could be valuable to many and highlights Perls strengths?
67
+
68
+ ----
69
+ !!! from here on the text is in raw state !!!
70
+ ----
71
+
72
+ useful
73
+ textinfo age
74
+ keep organized
75
+ multi purpose
61
76
62
77
63
78
64
79
[ Chapter Layout] ( #chapter-0 )
65
- --------------------------
80
+ ----------------------------
66
81
67
- The practical needs of the growing application did sometimes overrule the
68
- educational intents of the author. Nonetheless there is a golden thread
69
- and the menu (table of contents) as the index as well show where to find what.
82
+ The practical needs of the growing application shaped the content and ordering
83
+ of the chapter, sometimes even overruling the educational intents of the author.
84
+ Nonetheless there is a golden thread and the menu (table of contents) as the
85
+ index show where to find what.
70
86
71
- Every chapter has a main topic and several (mostly 6) ( often related) subtopics.
87
+ Every chapter has a main topic and several (mostly 6), often related subtopics.
72
88
Together they allow to bring the program to a new stage, introducing a new
73
89
feature set or a new style of programming. The source code in each stage is
74
- included (see table of content). Number in file names refer to a chapter.
90
+ included (see table of content). Numbers in file names refer to a chapter.
75
91
76
92
Each chapter has several paragraphs. They correspond to the subheadings in the table
77
- of content and covers only a single command, operator or another language feature.
93
+ of content and cover only a single command, operator or another language feature.
78
94
Usually they have just the right length to be read in 5 to 10 minutes.
79
- After that the tutorial can be easily put aside - to practice the new knowledge
80
- or to leave the train.
95
+ After that the tutorial can be easily put aside.
81
96
82
97
Chapters are also optimized for reading them in one swoop. The first paragraph(s)
83
98
are commonly an easy read - a warm up to get accustomed to the topic.
84
- The most challenging part is in the middle, while the end serves as a fade out
85
- and for reflection.
86
-
87
-
88
-
89
- [ What App To Build] ( #chapter-0 )
90
- ---------------------------
91
-
92
- useful
93
- textinfo age
94
- keep organized
95
- multi purpose
99
+ The most challenging part is iusually n the middle, while the end serves as a
100
+ fade out and for recap.
96
101
97
102
98
103
@@ -162,15 +167,20 @@ way you do the rest of the day.
162
167
163
168
[ Basic Syntax Rules] ( #chapter-0 )
164
169
--------------------------------
170
+ Mostly under Unix type operating systems like Linux, Irix, MaxOS and BSD you
171
+ can call text files like binary programs.
165
172
173
+ Every Perl 6 program starts
166
174
----
167
175
!!! from here on the text is in raw state !!!
168
176
----
177
+ #!/path/to/perl6
169
178
` use v6; `
170
-
171
- white space
179
+ new line
172
180
semicolon
181
+ white space
173
182
braces
183
+ slashes
174
184
175
185
176
186
@@ -184,6 +194,7 @@ not explaining details
184
194
185
195
` say slurp $?FILE; `
186
196
197
+
187
198
[ ^chapter start^] ( #chapter-0 )
188
199
189
200
[ ^^table of content^^] ( ../table-of-content.md )
0 commit comments