As late as last night I was able to use
Particle.variable without difficulty. All of a sudden I got a compile error, even on a program that was unchanged (i.e., I clicked Verify twice in a row without edits). I was briefly getting compile errors using
Time. as well, but that failure was transient and went away overnight.
I eventually found a year-old(!) bug report about this, and suggested fix, which worked:
What I’m wondering is why this is a transient error. I compile; it’s fine. I compile again without changing the program; it gives this error. I wait overnight and compile again; the
Time error disappears, the
Particle one does not. 24 hours later the
Particle error persists. I change the firmware setting and all is well.
But given that I never changed the firmware reading before, how did it ever compile? I’m starting to imagine a cloud of compile servers, all running slightly different compilers…and that’s kinda’ scary.
For the benefit of others who might find this thread using a search engine, here’s the concrete error message I got:
In file included from ../inc/spark_wiring.h:29:0, from ../inc/application.h:29, from dummytestbed.cpp:2: ../../core-common-lib/SPARK_Firmware_Driver/inc/config.h:12:2: warning: #warning "Defaulting to Release Build" [-Wcpp] #warning "Defaulting to Release Build" ^ dummytestbed.cpp: In function 'void setup()': dummytestbed.cpp:4:5: error: 'Particle' was not declared in this scope void loop(); ^ make: *** [dummytestbed.o] Error 1