aboutsummaryrefslogtreecommitdiff
path: root/vol1/2.4.lyx
blob: 24255acfc166d6dfcf0e8f883e586deda56d2db9 (plain)
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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
#LyX 2.4 created this file. For more info see https://www.lyx.org/
\lyxformat 620
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass book
\begin_preamble
\input defs
\end_preamble
\use_default_options true
\maintain_unincluded_children no
\language english
\language_package default
\inputencoding utf8
\fontencoding auto
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_roman_osf false
\font_sans_osf false
\font_typewriter_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\use_microtype false
\use_dash_ligatures true
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\float_placement class
\float_alignment class
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\use_formatted_ref 0
\use_minted 0
\use_lineno 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\is_math_indent 0
\math_numbering_side default
\quotes_style english
\dynamic_quotes 0
\papercolumns 1
\papersides 1
\paperpagestyle default
\tablestyle default
\tracking_changes false
\output_changes false
\change_bars false
\postpone_fragile_content false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\docbook_table_output 0
\docbook_mathml_prefix 1
\end_header

\begin_body

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
exerc1[00]
\end_layout

\end_inset

Considering COBOL data configurations as tree structures,
 are the data items listed by a COBOL programmer in preorder,
 postorder,
 or neither of these orders?
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
answer 
\end_layout

\end_inset

They are in preorder.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
exerc2[10]
\end_layout

\end_inset

Comment about the running time of Algorithm A.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
answer 
\end_layout

\end_inset

It takes a constant amount of time for each data item read (assuming that accessing the symbol table takes constant time).
 There is also a loop to get out of a nested record,
 but each iteration of the loop takes out an item from the stack so we may consider that as part of processing such item.
 Therefore the running time is proportional to the number of data items in the input.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
exerc8[10]
\end_layout

\end_inset

Under what circumstances is 
\begin_inset Quotes eld
\end_inset


\family typewriter
MOVE CORRESPONDING 
\begin_inset Formula $\alpha$
\end_inset

 TO 
\begin_inset Formula $\beta$
\end_inset


\family default

\begin_inset Quotes erd
\end_inset

 exactly the same as 
\begin_inset Quotes eld
\end_inset


\family typewriter
MOVE 
\begin_inset Formula $\alpha$
\end_inset

 TO 
\begin_inset Formula $\beta$
\end_inset


\family default

\begin_inset Quotes erd
\end_inset

,
 according to the definition in the text?
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
answer 
\end_layout

\end_inset

When 
\begin_inset Formula $\alpha$
\end_inset

 or 
\begin_inset Formula $\beta$
\end_inset

 is an elementary item.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
rexerc11[23]
\end_layout

\end_inset

What additional links or changes in the strategy of the algorithms of the text could make Algorithm B or Algorithm C faster?
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
answer 
\end_layout

\end_inset


\begin_inset Note Greyedout
status open

\begin_layout Plain Layout
(I had to look up the solution.)
\end_layout

\end_inset

 One could make Algorithm C faster by storing sibling nodes in the table in lexicographical order,
 so step C3 would have a linear rather than quadratic complexity.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
rexerc13[24]
\end_layout

\end_inset

Give an algorithm to substitute for Algorithm A when the Data Table is to have the format shown in exercise 12.
\end_layout

\begin_layout Standard
\begin_inset ERT
status open

\begin_layout Plain Layout


\backslash
answer 
\end_layout

\end_inset

We remove the instructions that set 
\family typewriter
PARENT
\family default
,
 
\family typewriter
CHILD
\family default
,
 
\family typewriter
SIB
\family default
,
 and 
\family typewriter
NAME
\family default
,
 as those fields do not exist now (in particular,
 A6 disappears),
 and we implement 
\begin_inset Formula $\mathtt{Q}\Leftarrow\mathtt{AVAIL}$
\end_inset

 in step A2 by sequential allocation.
 We set the 
\begin_inset Formula $\mathtt{SCOPE}$
\end_inset

 of an entry when we remove the corresponding item from the stack in step A5.
 (Note that we do the same in A5 when 
\begin_inset Formula $\mathtt{L1}=\mathtt{L}$
\end_inset

 as when 
\begin_inset Formula $\mathtt{L1}>\mathtt{L}$
\end_inset

,
 so we could just do those instructions unconditionally,
 then after removing the current stack item and before loading the next one we check if 
\begin_inset Formula $\mathtt{L1}=\mathtt{L}$
\end_inset

 and if so we go to A7,
 then if 
\begin_inset Formula $\mathtt{L1}\geq\mathtt{L}$
\end_inset

 we repeat,
 otherwise we report the error.)
\end_layout

\begin_layout Standard
For this to work,
 we have to get the stack empty by the time the algorithm finishes,
 which we can do by setting 
\begin_inset Formula $\mathtt{L}\gets0$
\end_inset

 when the input is exhausted in step A2 and then terminate in step A7 when 
\begin_inset Formula $\mathtt{L}=0$
\end_inset

.
\end_layout

\end_body
\end_document