> The problem is not the conditional compilation. That works just fine.
The problem here is that the attribute annotation is on a declare statement. AFAIK, that is not legal; we do not collect the corresponding context from the attributes pass.
So, from my point of view the problem here is that there was an inspection result for the missing attribute in the first place instead of one for an illegal annotation.
> FWIW, it seems to me we can at least add a description to the `Declare` statements.
``` Public Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long) Attribute Sleep.VB_Description = "Can I haz a description?" ``` 
I find it interesting that for module level variables, one must use VB_VarDescription whereas Declare has to use VB_Description just like other procedures.
I'm not sure why they thought it necessary to differentiate between a VB_VarDescription and VB_Description.
woah.... you can make a Declare statement a default member....
VBA Rubberducking
VBA Rubberducking