[Openmcl-devel] ~<...~> format directive

[R. Matthew Emerson]

http://trac.clozure.com/ccl/ticket/3 is a long-standing bug.
The question is: should (format t "~<Options: ~:>") signal
an error?

http://www.lispworks.com/documentation/HyperSpec/Body/22_ceb.htm
describes this directive.

As I read this description today, I'm leaning towards considering
ticket:3 as not a bug. (After all, an "arbitrary format string"
doesn't necessarily contain any directives.) Perversely enough,
however, I just committed a change that complains when ~<...~>
gets no arguments.

I'm now not sure what the correct behavior is.  I want ticket:3,
which has been mocking me for years now, to be resolved, but I'm
not sure that my so-called fix I just committed is even the right
thing.