Hello, world!\n
> Yes, exactly. In earlier versions, we forbade names that collide with
> keywords, but that caused compatibility issues when users upgrade to a
> new version, which may have new keywords that are accidentally the same
> as user-defined names. We changed that so a used-defined name overrides
> the keyword, so there is no compatibility problem, but it may lead to
> a strange behavior like this, as (due to how our parser is written) the
> name-keyword distinction is done independently of any context.
Perhaps it deserves a warning when parsing the configuration file then?
Martin
