Routine names accessible during runtime?

[weaver (Sam Weaver)]

If the DEBUG constant is defined during compilation, Inform 6 includes a printing rule called DebugAction (source) which, when given the number of the action can print its name.

Possible to determine the name of an action from an action number?

Followup to this post about Inform 7: I7 generates an I6 table array which holds all possible actions a player can take. It’s formatted like this: [a screenshot of the Inform 6 code used to specify the ActionData array] The actions in this array are specified using ## notation, which seems to be automatically converted to an “action number” by Inform 6. Is it possible to determine the name of an action associated with a particular action number at runtime? For example, something like this? …

Does anything similar exist to lookup the name of a routine?

[fredrik (Fredrik Ramsberg)]

I’m pretty sure the answer is no.

If you compile a game in debug mode or non-debug mode and then make a routine name a lot longer, the (unpadded) file length doesn’t change.

[Dannii]

Though if you’re compiling to Glulx you could include the debug file as a blorb resource chunk and then search it. Not simple to do though.