Not so much a bug as an inconsistency. Before leaving Kensington Gardens you may see the following message:
>WAIT
Time passes.
A log is being pushed across the Long Water by a pair of mallards. Its surface
is crowded with squirrels, chipmunks and other inhabitants of the Kensington
Gardens, including the roadrunner you met before. The ruby in its beak gleams
enticingly as the log sails through the white door.
The missile is closing in fast.
But even before this, MALLARDS-F will let you interact with them:
<ROUTINE MALLARDS-F ()
<COND (<VERB? FOLLOW WALK-TO>
<DO-WALK P?EAST>
<RTRUE>)>
<TELL ,CANT "see them anymore." CR>
<RFATAL>>
I think it would make sense if this worked more like, say, the bikes:
<ROUTINE BIKES-F ()
<COND (<NOT <IS? ,BIKES ,SEEN>>
<CANT-SEE-ANY>
<RFATAL>)>
<TELL ,CANT "see the " D ,BIKES " anymore." CR>
<RFATAL>>
(Not all such objects use SEEN. For instance, FLARE-F uses NODESC instead. But I think SEEN makes sense.)
Of course, the I-LONDON-HOLE routine will have to call <MAKE ,BIKES ,SEEN> for this to work.
Not so much a bug as an inconsistency. Before leaving Kensington Gardens you may see the following message:
But even before this,
MALLARDS-Fwill let you interact with them:I think it would make sense if this worked more like, say, the bikes:
(Not all such objects use
SEEN. For instance,FLARE-FusesNODESCinstead. But I thinkSEENmakes sense.)Of course, the
I-LONDON-HOLEroutine will have to call<MAKE ,BIKES ,SEEN>for this to work.