-
Notifications
You must be signed in to change notification settings - Fork 0
/
muf6.html
97 lines (78 loc) · 2.77 KB
/
muf6.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
<html>
<head>
<title>The MUCK Manual: Overview: MUF (6)</title>
</head>
<body bgcolor="#FFFFFF">
<center>
<a href="muf5.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="muf7.html">next</a>
</center>
<table>
<tr>
<td width="20%"> </tc>
<td>
<!-- BODY CONTENT HERE -->
<p><b>3.2 Overview: MUF (cont'd)</b></p>
<p><b>Organizing Your Code:</b></p>
<p>Recall that <code>MUF</code> is a `structured' language: as long as
the statements in a function are in the same order, reading top to
bottom and left to right, and as long as they are separated by
whitespace, it doesn't matter how you place them on the page.
`Whitespace' is any combination of spaces, tabs, or line breaks.</p>
<p>Instead of...</p>
<p><pre>
: main
me @ "Hello, world!" notify
"mink" "otter" "linsang"
pop pop pop
;
</pre></p>
<p>We could have written...</p>
<p><pre>
: main me @ "Hello, world!" notify "mink" "otter" "lingsang" pop pop pop ;
</pre></p>
<p>Or even...</p>
<p><pre>
: main me
@
"Hello, world!"
notify "mink"
"otter"
"linsang"
pop
pop
pop
;
</pre></p>
<p>All three versions would mean the same thing to the compiler, would use
the same amount of memory, and would be executed in exactly the same
way. To most people, however, the first version would be much more
clear. Arrange your code in such a way that its format illustrates or
reinforces logical relationships (that is, combine things that go
together and separate those that don't). </p>
<p><code>MUF</code> is not case sensitve: <code>POP,</code>
<code>Pop,</code> and <code>pop</code> would all be treated the same
way. Capitalization, therefore, can be used as another way to format
code. For example, you might choose to capitalize all function names and
begin all variable names with lower case to concisely indicate their
difference. Some coders use all capitals for primitives. This does
clearly indicate their difference, but many people find all caps less
readable than upper-lower case. Choose your own style, but remain
consistent within a program.</p>
<p>Now we'll (completely) rewrite tinker.muf several times, with each
version introducing an important aspect of <code>MUF</code> programming.
The > signs and other formatting information have been omitted from
the remaining examples, so you can cut and paste from this file into the
one you're working on.</p>
<center>
<a href="muf5.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="#top">top</a>|
<a href="muf7.html">next</a>
</center>
</td>
<td width="20%"> </tc>
</table>
</body>
</html>