Re: [Tads3] knowledge / 'seen' / npc knowledge base

[Jesse Welton <jwelton@xxxxxxxxxxxxxxxxxxxxxxxxxx>]

Mike Roberts wrote:
> 
> The keys would be the objects; the values would be arbitrary, as it's the 
> presence in the table we care about, much as it's the presence in the vector 
> we care about.  The only difference is that testing for presence in a lookup 
> table is faster.  The tables would be per NPC.

It sounds to me like this calls for an actual Set collection class,
which could be implemented much like the LookupTable, but saving a
little space by dropping the values.  On the other hand, there might
be uses for the values in some situations, such as indicating varying
levels of knowledge about some subject.

-Jesse