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

[Tim Bradshaw]

On 9 Aug 2011, at 03:42, R. Matthew Emerson wrote:

> 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 think it probably should complain: if the format string does not eat anything from the list, there should at least be a list *there*, though it may be null.