List of Objects shows numbers instead of Object name

Running the following test code:

Lab is a room.

A power is a kind of object.

A power list is a list of powers that varies.
The power list is usually {}.

To upload (power - a power) to suit:
	if power is not listed in power list:
		add power to the power list;
		say "You upload [power] to suit.";
	otherwise:
		say "You already uploaded the [power] power.".

To remove (power - a power) from suit:
	if power is listed in power list:
		remove power from the power list;
		say "You remove [power] from suit.";
	otherwise:
		say "You already removed the [power] power.".

Super Punch is a power.

Fooing is an action applying to nothing.
Understand "foo" as fooing.
Instead of fooing:
	upload Super Punch to suit.

Barring is an action applying to nothing.
Understand "bar" as barring.
Instead of barring:
	remove Super Punch from suit.

Bazzing is an action applying to nothing.
Understand "baz" as bazzing.
Instead of bazzing:
	say "Power List: [power list][line break]".

Expected Behavior:

>foo
You upload Super Punch to suit.

>baz
Power List: Super Punch

Observed Behavior:

>foo
You upload Super Punch to suit.

>baz
Power List: 58158

Avoid explicitly declaring the list as an empty list. It’s the line:

The power list is usually {}.

that’s causing the issue. It’s not necessary, as the line:

A power list is a list of powers that varies.

will have already set it up as an empty list.

The same problem showed up in Having trouble with list equality.

3 Likes

Bug first mentioned (I think) in this thread: Displaying list gives numbers (reference address?) not names

1 Like

Should I be checking for and/or filing these bugs at Log in with Atlassian account?

Is it okay to just get an account and start filing or is it being triaged in some way?

This behavior doesn’t occur in v10, so there’s no need for a bug report. But, yes, anyone can get an account and file bugs. Whatever triaging is happening is being done by Graham, I presume…

Sounds good, thanks for the info.

I found the resolved bug report for anyone who is interested.

Just got Inform 10.1.1 up and running today (via the Mac IDE), and I can also confirm that this issue has been fixed.