The INCREMENT-TIME routine has a case for printing messages about the sun rising and setting at the Research Center Rooftop:
<COND (<EQUAL? ,HERE ,ROOF>
<COND (<EQUAL? ,TIME 348>
<TELL CR
"The first glow of dawn appears on the horizon." CR>)
(<EQUAL? ,TIME 378>
<TELL CR
"The sun is now well above the horizon; day has begun." CR>)
(<EQUAL? ,TIME 1073>
<TELL CR
"The sky begins to darken as the sun sinks into the western sky." CR>)
(<EQUAL? ,TIME 1103>
<TELL CR
"The last glow of dusk fades as nighttime falls across the rooftop." CR>)>)>)>
These messages are never printed, and as far as I can tell there are two reasons for this:
The Research Center Rooftop is ROOFTOP. ROOF is an object in the Research Center Rooftop room.
The whole thing is inside the <G? ,TIME 1439>, i.e. when the next day begins. There's no sensible way it could hit any of the cases.
Theoretically, the routine could also be called with X greater than 1, which would cause it to skip the specific times it's checking for. But I don't think that can ever happen at the rooftop.
Changing ROOF to ROOFTOP and moving the COND out of the <G? ,TIME 1439> case seemed to work fine when I tried it.
The
INCREMENT-TIME
routine has a case for printing messages about the sun rising and setting at the Research Center Rooftop:These messages are never printed, and as far as I can tell there are two reasons for this:
ROOFTOP
.ROOF
is an object in the Research Center Rooftop room.<G? ,TIME 1439>
, i.e. when the next day begins. There's no sensible way it could hit any of the cases.Theoretically, the routine could also be called with
X
greater than 1, which would cause it to skip the specific times it's checking for. But I don't think that can ever happen at the rooftop.Changing
ROOF
toROOFTOP
and moving theCOND
out of the<G? ,TIME 1439>
case seemed to work fine when I tried it.