ESP8266 Community Forum

- Fri May 08, 2020 8:33 pm #86984

why #include <WiFiUdp.h>?

You are right. The ESP lib works without that include.
Does it include it implicitly?
Or ist is querying NTP with all the ballast of HTTP?

- Sat May 09, 2020 3:59 am #86995

...we don't care about ESP32.

Who is "we"?
There may be people here as well, who are not blinkered and think further, while they are coding.

people here - and the relevant ones over at github - decided against the *not working* espressif implementation ...

... why change a working system?

I explained why.

no you postulated ...

- Sat May 09, 2020 4:14 am #86996

people here - and the relevant ones over at github - decided against the *not working* espressif implementation ...

I never postulated the Espressif implementation were not working.
What makes you think that?

Just at the opposite! Indeed -it's already in the title- I am elaborating on getting rid of counter-productive no-espressif libraries nested into many examples lurking around.

I have worked out a didactic example on how to use it and produce what most subsequent Arduino libs and applications need.

- Sat May 09, 2020 4:01 pm #87002 you (explained) postulated the need for changing the runing system. I said there is no need to.

with the recent core there is no need for "another time lib for ESP" (not any!, not even ntpclient!) in line with your topic but in contrary to your suggested solution.

Sketches that compile on esp8266 and esp32 without taking care of other major differences (beside timelib) probably are sparse. But even the "time lib problem" could easily be solved via conditional code blocks.