Lines Matching full:should

10 This code should be replaced with code like:
29 This code should be replaced with code like:
49 This code should be replaced with code like:
67 This code should be replaced with code like:
73 Both format should consume the same number of arguments off the stack
85 This code should be replaced with code like:
100 This code should be replaced with code like:
137 in it, like "{N:Type of I/O}"; backslashes should be escaped,
151 This code should be replaced with code like:
169 This code should be replaced with code like:
193 This code should be replaced with code like:
212 This code should be replaced with code like:
231 This code should be replaced with code like:
251 This code should be replaced with code like:
259 But the raw field name should use hyphens.
271 This code should be replaced with code like:
280 'Value field name should be lower case'
283 The message "Value field name should be lower case" can be caused by code like:
289 This code should be replaced with code like:
295 Lower case is more civilized. Even TLAs should be lower case
300 'Value field name should be longer than two characters'
303 The message "Value field name should be longer than two characters" can be caused by code like:
309 This code should be replaced with code like:
315 Field names should be descriptive, and it's hard to
332 This code should be replaced with code like:
352 This code should be replaced with code like:
358 This is minor, but fields should use proper roles. Decoration
364 'Anchor content should be decimal width'
367 The message "Anchor content should be decimal width" can be caused by code like:
373 This code should be replaced with code like:
386 'Anchor format should be "%d"'
389 The message "Anchor format should be "%d"" can be caused by code like:
395 This code should be replaced with code like:
415 This code should be replaced with code like:
434 This code should be replaced with code like:
444 like "{:tag/%6..6d}" where only one period should be used.