Hi,

I am going to assume you are using Visual Studio and not Atmel Studio.

In Visual Studio we currently use the VC++ intellisense which isn't perfect.

Microsoft has released some better tools in the past year or so, such as Clang and we might shortly move to using what should be a better system for intellisense. I am not sure how it will cope with assembly code but in theory much better.

Breaking code over multiple lines is probably an unsolvable problem for VC++ however for some other errors can be prevented as follows:-

Add a .h to the project but do not need to #include from any code. Then use the standard _MSC_VER variable to make alternative definitions that intellisense will be happy with.

Obviously if there are many different intellisense errors this isn't a practical solution but so far it's been ok for most.

Example:-

#pragma once

#if _MSC_VER

//insert dummy defs here
//ie: digitalWrite(int, int){}

#endif 

If this issue becomes too difficult to manage you can consider using the Atmel Studio version of Visual Micro. Atmel Studio understands Gcc but isn't quite as full an IDE as Visual Studio.

Interested to hear your thoughts