This is an advice for an alternative way to use the Arduino ino-file as a pure project-file that I have not seen. Folks like me prefer this standard-structure to put code in different folder tree-structures, and as well it avoids c-code in ino-files that is little odd and might require several actions in external tools.
My typical ino-file looks like following with no more c-code. Arduino error messages will correct refer the actual file and line:
(trying code-tags but does not know the format here)
- Arduino project and startup file.
// PROJECT FILES. NOTICE C/CPP files:
// ARDUINO STARTUP and LOOP: