I suggest you ...

Allow conditions in table entries

Allow conditions either directly:

Table of Conditions
column-name
condition
the player is carrying a book

or truth states evaluated at runtime:

Table of Conditions
column-name
truth state
whether or not the player is carrying a book

4 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JuhanaJuhana shared this idea  ·   ·  Admin →
    declined  ·  emshortAdminemshort (Admin, Inform 7) responded  · 

    This is not allowed. Firstly because table entries are constant data, that is, data whose value can be determined before the start of play, like numbers, texts, and so on. Truth state columns are legal, but the only legal entries in them are “true” and “false”. What you have here would be a column whose kind would implicitly have to be “phrase nothing → truth state”, and that would not only be tricky to compile, it would be very misleading. People might try to set an entry to “true” during play and – if this even compiled, because it has the wrong kind, properly speaking – people would think this made the condition come true; whereas in fact it would destroy the original condition test. (Compare, for example, the C language, where arrays can’t be legally initialised with variable names among the values.)

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Ron NewcombRon Newcomb commented  · 

        ...or add anonymous functions to Inform. :)

      Feedback and Knowledge Base