From ada5eb55cb185edf30dcac48b25cc485d44677ef Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Sat, 22 Oct 2016 12:08:10 -0700 Subject: 3552 Stop requiring jump instructions to explicitly provide a ':label' type for jump targets. This has been a source of repeated confusion for my students: a) They'd add the ':label' to the label definition rather than the jump target (label use) b) They'd spend time thinking about whether the initial '+' prefix was part of the label name. In the process I cleaned up a couple of things: - the space of names is more cleanly partitioned into labels and non-labels (clarifying that '_' and '-' are non-label prefixes) - you can't use label names as regular variables anymore - you can infer the type of a label just from its name --- lambda-to-mu.mu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lambda-to-mu.mu') diff --git a/lambda-to-mu.mu b/lambda-to-mu.mu index 6c358d9f..4cd9da7d 100644 --- a/lambda-to-mu.mu +++ b/lambda-to-mu.mu @@ -232,7 +232,7 @@ def parse in:&:stream:char -> out:&:cell, in:&:stream:char [ close-paren?:bool <- equal c, 41/close-paren break-unless close-paren? read in # skip ')' - break +end-pair:label + break +end-pair } # still here? read next element of pair next:&:cell, in <- parse in -- cgit 1.4.1-2-gfad0 akkartik/mu/refs/?h=hlt&id=e3c74453309a685594b93f344cba9cb59b7ac456'>refs log blame commit diff stats
path: root/102keyboard.subx
blob: 39788075881d091fe0aee458c31738dfe4f4d3f9 (plain) (tree) 
be87d723 ^


6e36ce06 ^



32bb01ba ^



143cce94 ^












be87d723 ^













3a0664e1 ^





3844651e ^

eede9e22 ^

be87d723 ^


be87d723 ^

3a0664e1 ^



be87d723 ^













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