I suggest you ...

The IDE interpreter should reject invalid Glk calls

There are several common mistake patterns for erroneous Glk calls:

- Calling a window function (e.g. glk_window_clear) with a window argument of zero, or a window argument that doesn't refer to a real window

- Ditto for stream and sound-channel function.

- Printing to a text window which is awaiting line input.

These are fatal errors on some Glk libraries, but are ignored on others. (Or they're ignored by default, with a "strict mode" preference.) This leads authors into a trap, like the "vile zero" situation on the Z-machine a decade ago.

To avoid this, the IDE interpreter's Glk library should be strict about these errors, and always bring them to the author's notice.

6 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…)
    Andrew PlotkinAndrew Plotkin shared this idea  ·   ·  Admin →

    0 comments

    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...

      Feedback and Knowledge Base