1
0
Fork 0
mirror of https://github.com/ganelson/inform.git synced 2024-07-02 23:14:57 +03:00

Fix for Mantis bug 1912

This commit is contained in:
Graham Nelson 2022-04-11 23:58:12 +01:00
parent ae46105e51
commit b110c6d86c
2 changed files with 14 additions and 13 deletions

View file

@ -1,15 +1,16 @@
Inform 7 build 6L26 has started. Inform 7 v10.1.0 has started.
I've now read your source text, which is 64 words long. I've now read your source text, which is 64 words long.
I've also read Standard Rules by Graham Nelson, which is 42597 words long. I've also read Basic Inform by Graham Nelson, which is 7691 words long.
I've also read English Language by Graham Nelson, which is 2288 words long. I've also read English Language by Graham Nelson, which is 2328 words long.
I've also read Standard Rules by Graham Nelson, which is 32092 words long.
Problem__ PM_CantUncreate Problem__ PM_CantUncreate
>--> In order to act on 'The winch switch states are lock, free, reel in, run >--> In order to act on 'The winch switch states are lock, free, reel in, run
out' (source text, line 3), I seem to need to give a new meaning to 'lock', out' (source text, line 3), I seem to need to give a new meaning to 'lock',
something which was created by the earlier sentence 'The lock is scenery in which currently means something created by the earlier sentence 'The lock
the Service Area' (source text, line 2). That must be wrong somehow: I'm is scenery in the Service Area' (source text, line 2). That must be wrong,
guessing that there is an accidental clash of names. This sometimes happens so I'm guessing that there is an accidental clash of names. This sometimes
when adjectives are being made after objects whose names include them: for happens when adjectives are being made after objects whose names include
instance, defining 'big' as an adjective after having already made a 'big them: for instance, defining 'big' as an adjective after having already
top'. The simplest way to avoid this is to define the adjectives in made a 'big top'. The simplest way to avoid this is to define the
question first. adjectives in question first.
Inform 7 has finished: 17 centiseconds used. Inform 7 has finished.

View file

@ -1883,8 +1883,8 @@ void Assertions::issue_value_equation_problem(parse_node *px, parse_node *py) {
StandardProblems::handmade_problem(Task::syntax_tree(), _p_(PM_CantUncreate)); StandardProblems::handmade_problem(Task::syntax_tree(), _p_(PM_CantUncreate));
Problems::issue_problem_segment( Problems::issue_problem_segment(
"In order to act on %2, I seem to need to give " "In order to act on %2, I seem to need to give "
"a new meaning to '%1', something which was created by the earlier " "a new meaning to '%1', which currently means something created by the "
"sentence %3. That must be wrong somehow: I'm guessing that there " "earlier sentence %3. That must be wrong, so I'm guessing that there "
"is an accidental clash of names. This sometimes happens when " "is an accidental clash of names. This sometimes happens when "
"adjectives are being made after objects whose names include them: " "adjectives are being made after objects whose names include them: "
"for instance, defining 'big' as an adjective after having already " "for instance, defining 'big' as an adjective after having already "