TADS/adv3 bug: >FOO, BAR throws an error

Crosslinking with another solution @BrettW provided.

modify TryAsActorResolveResults
    unknownNounPhrase(match, resolver) { return []; }
;

Both solutions seem to result in the same user message The story doesn't understand that command. Any reason to prefer one solution over the other? If I’m following things right, Brett’s solution provides an expected return value and so avoids the error, while the former traps and masks it? The mask feels less elegant?

1 Like