Unreacheable code detected about rubberduck HOT 6 CLOSED

Hi guys,

I like what you've created here. I really want to use it, but this particular issue is something of a stumbling block for me. Where I work we have a couple of corporate XL add ins with protected code. Every time I open up one of Rubberduck menus (e.g the to dos). I get a pop up warning that it's found some code that it doesn't know how to analyse. Any idea when this particular issue might be fixed? It would be awesome if it can ignore the protected code a bit more quietly :-)

Cheers,
Andy

from rubberduck.

Hi there @bigandyherd! We're really happy you like what we've done so far. I've opened issue #289 and added it to our our next milestone. I'd like to fix this in the next release if possible, but it might get bumped to the one after depending on time constraints.

from rubberduck.

Thanks @ckuhn203, I'll keep a lookout :-)

from rubberduck.

You're welcome @bigandyherd! 👍 Make sure to subscribe to the other issue so you'll get notifications.

from rubberduck.

As of version 1.21, locked projects will show up like this in the Code Explorer:

Also the parser will now check to see if a project is locked before it tries to access its components.

from rubberduck.

Detecting unreacheable code implies simulating the compiler... which is a little bit beyond the scope of this project.

from rubberduck.