-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathday9.p
106 lines (89 loc) · 3.86 KB
/
day9.p
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
98
99
100
101
102
103
104
105
106
/*
--- Day 9: Encoding Error ---
With your neighbor happily enjoying their video game, you turn your attention to an open data port on the little screen in the seat in front of you.
Though the port is non-standard, you manage to connect it to your computer through the clever use of several paperclips. Upon connection, the port outputs a series of numbers (your puzzle input).
The data appears to be encrypted with the eXchange-Masking Addition System (XMAS) which, conveniently for you, is an old cypher with an important weakness.
XMAS starts by transmitting a preamble of 25 numbers. After that, each number you receive should be the sum of any two of the 25 immediately previous numbers. The two numbers will have different values, and there might be more than one such pair.
For example, suppose your preamble consists of the numbers 1 through 25 in a random order. To be valid, the next number must be the sum of two of those numbers:
26 would be a valid next number, as it could be 1 plus 25 (or many other pairs, like 2 and 24).
49 would be a valid next number, as it is the sum of 24 and 25.
100 would not be valid; no two of the previous 25 numbers sum to 100.
50 would also not be valid; although 25 appears in the previous 25 numbers, the two numbers in the pair must be different.
Suppose the 26th number is 45, and the first number (no longer an option, as it is more than 25 numbers ago) was 20. Now, for the next number to be valid, there needs to be some pair of numbers among 1-19, 21-25, or 45 that add up to it:
26 would still be a valid next number, as 1 and 25 are still within the previous 25 numbers.
65 would not be valid, as no two of the available numbers sum to it.
64 and 66 would both be valid, as they are the result of 19+45 and 21+45 respectively.
Here is a larger example which only considers the previous 5 numbers (and has a preamble of length 5):
35
20
15
25
47
40
62
55
65
95
102
117
150
182
127
219
299
277
309
576
In this example, after the 5-number preamble, almost every number is the sum of two of the previous 5 numbers; the only number that does not follow this rule is 127.
The first step of attacking the weakness in the XMAS data is to find the first number in the list (after the preamble) which is not the sum of two of the 25 numbers before it. What is the first number that does not have this property?
*/
DEFINE VARIABLE cLine AS CHARACTER NO-UNDO.
DEFINE VARIABLE iNumber AS INT64 EXTENT 25 NO-UNDO.
DEFINE VARIABLE iCurrent AS INT64 NO-UNDO.
DEFINE VARIABLE iPos AS INTEGER INITIAL 1 NO-UNDO.
DEFINE VARIABLE lInitializing AS LOGICAL INITIAL TRUE NO-UNDO.
DEFINE VARIABLE i AS INTEGER NO-UNDO.
DEFINE VARIABLE j AS INTEGER NO-UNDO.
DEFINE VARIABLE lFound AS LOGICAL NO-UNDO.
ETIME(TRUE).
INPUT FROM C:\Work\aoc\aoc2020\day9.txt.
REPEAT:
IMPORT UNFORMATTED cLine.
iCurrent = INT64(cLine).
IF lInitializing THEN DO:
iNumber[iPos] = iCurrent.
iPos = iPos + 1.
IF iPos > 25 THEN ASSIGN
iPos = 1
lInitializing = NO.
END.
ELSE DO:
lFound = NO.
blkSearch:
DO i = 1 TO 25:
DO j = i TO 25:
IF iNumber[i] + iNumber[j] = iCurrent THEN DO:
lFound = YES.
LEAVE blkSearch.
END.
END.
END.
IF NOT lFound THEN LEAVE.
iNumber[iPos] = iCurrent.
iPos = iPos + 1.
IF iPos > 25 THEN iPos = 1.
END.
END.
INPUT CLOSE.
MESSAGE etime skip iCurrent
VIEW-AS ALERT-BOX INFO BUTTONS OK.
/*
---------------------------
Renseignement (Press HELP to view stack trace)
---------------------------
140
14144619
---------------------------
OK Aide
---------------------------
*/