On Mon, Apr 14, 2003 at 09:42:53PM +0200, Kjetil Torgrim Homme wrote:
(somewhere at the start of the specification:)
A constant string is a string or multi-line value without variable
(in a section on interactions with old and new mechanisms?)
Implementations MAY require match patterns to be constant strings
when used with some test types. Such implementations MUST reject
the activation of scripts with disallowed match patterns.
is it too strong to require the error to be discovered at upload time?
I don't feel good about allowing it to happen during run-time, but
that might be a quality-of-implementation issue.
Hm. That's a reasonable offer, Kjetil, but I'd rather eat
the complexity as an implementor than to place it on the users
and client writers by making this be an implementation-specific