> Maybe there's an interesting little parser patch here. Say a piece of
sugar that converts
> object!.name
> to
> (
object.name or error("'object' lacks
required field 'name'"))
“or” isn’t quite what is wanted here, is it? it would (undesirably)
catch object.name == false (as opposed to just nil).
- Peter