git.iko.soy/urbit.org
on master help sign in
Merge pull request #399 from baudtack/restoration

Restore proper pronunciation guide

commita5190338db7b745a52544a9ddf510f243fbb0b20 authorpilfer-pandex <47340789+pilfer-pandex@users.noreply.github.com> dateSat 16 Mar 2019, 17:46 (8 years ago) parent4352a838cf1fb8
8 files changed+50−48
compare with master
unifiedsplit
learn/arvo/hoon/hoon-syntax.udon+17−15 reference/glossary.udon+12−12 reference/hoon-expressions/rune.udon+1−1 reference/hoon-expressions/rune/bus.udon → reference/hoon-expressions/rune/buc.udon+14−14 reference/hoon-expressions/rune/lus.udon+1−1 reference/hoon-expressions/rune/mic.udon+1−1 reference/hoon-expressions/rune/sig.udon+2−2 reference/hoon-expressions/rune/tis.udon+2−2
learn/arvo/hoon/hoon-syntax.udon+17−15
@@ -36,21 +36,23 @@ Hoon source files are composed almost entirely of the [printable ASCII character
3636Hoon code makes heavy use of non-alphanumeric symbols. Reading off code aloud using the proper names of ASCII symbols is tedious, so we've mapped syllables to symbols:
3737
3838```
39−ace [1 space] hep - rob }
40−ban > ket ^ say '
41−bar | lac [ sig ~
42−bat \ led < tar *
43−bus $ lit ( tec `
44−cab _ lob { tis =
45−cen % lus + vat @
46−col : mic ; wut ?
47−com , net / yel "
48−dot . pad & zap !
49−gap [>1 space, nl] rac ]
50−hax # rit )
51−```
52−
53−Learning and using these names of non-alphanumeric symbols is entirely optional; you can become an expert Hoon programmer without them. Many Hoon programmers find them helpful, however, particularly when talking to someone else who knows them.
39+ace [1 space] gal < pal (
40+bar | gap [>1 space, nl] par )
41+bas \ gar > sel [
42+buc $ hax # mic ;
43+cab _ hep - ser ]
44+cen % kel { sig ~
45+col : ker } soq '
46+com , ket ^ tar *
47+doq " lus + tic `
48+dot . pam & tis =
49+fas / pat @ wut ?
50+zap !
51+```
52+
53+Learning and using these names of non-alphanumeric symbols is entirely optional; you can become an expert Hoon programmer without them. Many Hoon programmers find them helpful, however, par
54+
55+ularly when talking to someone else who knows them.
5456
5557Note that the list includes two separate whitespace forms: `ace` for a single space; `gap` is either 2+ spaces or a newline. In Hoon, the only whitespace significance is the distinction between `ace` and `gap` -- i.e., the distinction between one space and more than one.
5658
reference/glossary.udon+12−12
@@ -420,18 +420,18 @@ information in speech. [`Runes`](#rune) are composed of two glyphs.
420420Below is a complete list of glyphs with their associated pronunciations.
421421
422422```
423−ace [1 space] hep - rob }
424−ban > ket ^ say '
425−bar | lac [ sig ~
426−bat \ led < tar *
427−bus $ lit ( tec `
428−cab _ lob { tis =
429−cen % lus + vat @
430−col : mic ; wut ?
431−com , net / yel "
432−dot . pad & zap !
433−gap [>1 space, nl] rac ]
434−hax # rit )
423+ace [1 space] gal < pal (
424+bar | gap [>1 space, nl] par )
425+bas \ gar > sel [
426+buc $ hax # mic ;
427+cab _ hep - ser ]
428+cen % kel { sig ~
429+col : ker } soq '
430+com , ket ^ tar *
431+doq " lus + tic `
432+dot . pam & tis =
433+fas / pat @ wut ?
434+zap !
435435```
436436
437437### Hall
reference/hoon-expressions/rune.udon+1−1
@@ -56,7 +56,7 @@ Runes used for making function calls in Hoon.
5656
5757Runes that let us adjust types without violating type constraints.
5858
59−### [`$ bus` (Structures)](bus)
59+### [`$ buc` (Structures)](buc)
6060
6161Runes used for defining custom types.
6262
reference/hoon-expressions/rune/bus.udon → reference/hoon-expressions/rune/buc.udonrenamed+14−14
@@ -1,11 +1,11 @@
11:- :~ navhome/'/docs/'
22 next/'true'
33 sort/'12'
4− title/'Structures $ ("bus")'
4+ title/'Structures $ ("buc")'
55 ==
66;>
77
8−# Structures $ ("bus")
8+# Structures $ ("buc")
99
1010The `$` family of runes is used for defining custom types. Strictly speaking,
1111these runes are used to produce 'structures'. A structure is a compile-time
@@ -61,7 +61,7 @@ Irregular: `*` makes `%noun`, `^` makes `%cell`, `?` makes
6161
6262;=
6363 ;h3
64− ;div(id "buscab"): $_ "buscab"
64+ ;div(id "buccab"): $_ "buccab"
6565 ==
6666==
6767
@@ -101,7 +101,7 @@ and produces its *example* instead.
101101
102102;=
103103 ;h3
104− ;div(id "buscen"): $% "buscen"
104+ ;div(id "buccen"): $% "buccen"
105105 ==
106106==
107107
@@ -136,7 +136,7 @@ be an infinite loop!
136136
137137;=
138138 ;h3
139− ;div(id "buscol"): $: "buscol"
139+ ;div(id "buccol"): $: "buccol"
140140 ==
141141==
142142
@@ -174,7 +174,7 @@ Irregular (structure mode): `[a b c]` is `$:(a b c)`.
174174
175175;=
176176 ;h3
177− ;div(id "bushep"): $- "bushep"
177+ ;div(id "buchep"): $- "buchep"
178178 ==
179179==
180180
@@ -193,7 +193,7 @@ Regular: *2-fixed*.
193193
194194##### Discussion
195195
196−Since a `$-` reduces to a [`$_`](#buscab), it is not useful for normalizing, just for typechecking. In particular, the existence of `$-`s does *not* let us send gates or other cores over the network!
196+Since a `$-` reduces to a [`$_`](#buccab), it is not useful for normalizing, just for typechecking. In particular, the existence of `$-`s does *not* let us send gates or other cores over the faswork!
197197
198198##### Examples
199199
@@ -206,7 +206,7 @@ Since a `$-` reduces to a [`$_`](#buscab), it is not useful for normalizing, jus
206206
207207;=
208208 ;h3
209− ;div(id "busket"): $^ "busket"
209+ ;div(id "bucket"): $^ "bucket"
210210 ==
211211==
212212
@@ -244,7 +244,7 @@ Regular: *2-fixed*.
244244
245245;=
246246 ;h3
247− ;div(id "bussig"): $~ "bussig"
247+ ;div(id "bucsig"): $~ "bucsig"
248248 ==
249249==
250250
@@ -311,7 +311,7 @@ Using `$~`:
311311
312312;=
313313 ;h3
314− ;div(id "busvat"): $@ "busvat"
314+ ;div(id "bucvat"): $@ "bucvat"
315315 ==
316316==
317317
@@ -353,7 +353,7 @@ Example:
353353
354354;=
355355 ;h3
356− ;div(id "bustis"): $= "bustis"
356+ ;div(id "buctis"): $= "buctis"
357357 ==
358358==
359359
@@ -392,7 +392,7 @@ p=%foo
392392
393393;=
394394 ;h3
395− ;div(id "buswut"): $? "buswut"
395+ ;div(id "bucwut"): $? "bucwut"
396396 ==
397397==
398398
@@ -417,8 +417,8 @@ Irregular: `?(%foo %baz)` is `$?(%foo %baz)`.
417417##### Discussion
418418
419419For a union of atoms, a `$?` is fine. For more complex nouns,
420−always try to use a [`$%`](#buscen), [`$@`](#busvat) or
421−[`$^`](#bushep), at least if you expect your structure to be used as a
420+always try to use a [`$%`](#buccen), [`$@`](#bucpat) or
421+[`$^`](#buchep), at least if you expect your structure to be used as a
422422normalizer.
423423
424424##### Examples
reference/hoon-expressions/rune/lus.udon+1−1
@@ -69,7 +69,7 @@ Notice that `p.q` has the label `%numbers`. Contrast with:
6969
7070;=
7171 ;h3
72− ;div(id "lusbus"): +$ "lusbus"
72+ ;div(id "lusbuc"): +$ "lusbuc"
7373 ==
7474==
7575
reference/hoon-expressions/rune/mic.udon+1−1
@@ -176,7 +176,7 @@ Fails because not a fixpoint:
176176
177177;=
178178 ;h3
179− ;div(id "micnet"): ;/ "micnet"
179+ ;div(id "micfas"): ;/ "micfas"
180180 ==
181181==
182182
reference/hoon-expressions/rune/sig.udon+2−2
@@ -86,7 +86,7 @@ ford: build failed
8686
8787;=
8888 ;h3
89− ;div(id "sigbus"): ~$ "sigbus"
89+ ;div(id "sigbuc"): ~$ "sigbuc"
9090 ==
9191==
9292
@@ -318,7 +318,7 @@ This should work fine:
318318
319319;=
320320 ;h3
321− ;div(id "signet"): ~/ "signet"
321+ ;div(id "sigfas"): ~/ "signet"
322322 ==
323323==
324324
reference/hoon-expressions/rune/tis.udon+2−2
@@ -381,7 +381,7 @@ Regular: *3-fixed*.
381381
382382;=
383383 ;h3
384− ;div(id "tisnet"): =/ "tisnet"
384+ ;div(id "tisfas"): =/ "tisfas"
385385 ==
386386==
387387
@@ -418,7 +418,7 @@ Regular: *3-fixed*.
418418##### Discussion
419419
420420`p` can be either a name or a name=type. If it's just a name,
421−`=/` ("tisnet") "declares a type-inferred variable." If it has a type, `=/`
421+`=/` ("tisfas") "declares a type-inferred variable." If it has a type, `=/`
422422"declares a type-checked variable."
423423
424424##### Examples