Go Down

Topic: why ignore bad #includes? (Read 471 times) previous topic - next topic

gardner

I believe it is a bug that 1.0.5 compiles this without error.

Code: [Select]
#include <it_just_plain_isnt/there/at/all.h>

void setup() {
  // put your setup code here, to run once:

}

void loop() {
  // put your main code here, to run repeatedly:
 
}


I just spent a half hour messing with a library that wanted #include <stdint.h> when I had mistakenly put #include <sys/types.h>.  GCC will definitely notice if a whole include is not found.  Why have Arduino just ignore this situation?

Go Up
 


Please enter a valid email to subscribe

Confirm your email address

We need to confirm your email address.
To complete the subscription, please click the link in the email we just sent you.

Thank you for subscribing!

Arduino
via Egeo 16
Torino, 10131
Italy