I’m trying to control how assemblies are grouped together statements with assemblies.
Basically any behavior other than the default would be great.
[code]“Noodles” by “Anonymous Girly-Girl”
The Locker Room is a room.
Ownership relates a person (called the owner) to a thing. The verb to own means the ownership relation.
A cheerleader is a kind of woman.
Betsy and Alice are cheerleaders in the locker room.
A cheer locker is a kind of fixed in place container.
A cheer locker is usually openable and closed. [and locked, but for demo purposes not so much]
Every cheerleader owns a cheer locker (called her locker) which is within the locker room.
Rule for printing the name of a cheer locker: say “[owner]'s Locker”.
First before listing contents: group cheer lockers together as “lockers”.
Understand “locker for [something related by reversed ownership]” as a cheer locker.
In the locker room are 5 cheer lockers.
Dana and Carla are a women in the locker room.
Carla’s Locker is a cheer locker owned by Carla. It is here.
Dana’s Locker is a cheer locker owned by Dana. It is here.
test me with “open locker for alice / look”[/code]
The lockers that weren’t created with assemblies are fine (of course)
If I open Alice or Betsy’s locker I get a listing that looks right.
Is there some way to control equality/equivalence rules? That might do the trick too. It looks like the lockers being created by “Every cheerleader owns a cheer locker…” and “In the locker room are 5 cheer lockers.” are treated the same.
I experimented with using a pre-processor before. I may have to start doing that again…
A good rundown of what can and cannot be done with assemblies might be nice if someone has the time to explain it all.