[closer-devel] New warning "No generic function F present	when	encountering macroexpansion of defmethod."
    Pascal Costanza 
    pc at p-cos.net
       
    Wed Nov  4 13:51:09 UTC 2009
    
    
  
On 4 Nov 2009, at 14:07, Attila Lendvai wrote:
>>>> How about a compiler note instead?
>>>
>>> Is there a portable way to emit compiler notes? I don't immediately
>>> find anything in the HyperSpec.
>>
>> Signal a STYLE-WARNING, it's what it's for.
>
>
> yes, and sane compilers already signal a style warning for this, while
> the conflict with cl:defmethod is kinda cumbersome. needs to be dealt
> with at every usage of closer mop... is it worth it?
OK, a style warning seems reasonable.
I will check which compilers already issue such a style warning, and  
only include the warning for implementations that don't do this. If  
there is a common way of disabling such style warnings, I will try to  
integrate that as well, hopefully in a uniform way.
> maybe as part of a closer-mop-strict package?
I'm not sure if I would want that. I think the right way is to use a  
global variable, a symbol macro, or an entry in *features*. I will  
check what is best.
Thanks a lot for the feedback!
Pascal
-- 
Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net
Vrije Universiteit Brussel
Software Languages Lab
Pleinlaan 2, B-1050 Brussel, Belgium
    
    
More information about the closer-devel
mailing list