- Fri Aug 03, 2018 6:00 pm
#77573
There are serious inconsistencies w.r.t date structures we have time_t a 32bit stamp based on elapsed seconds either 1900 or 1970
There are naming issues Month mon etc
There are inconsistent structures DateTime uses tmElements and tm
The index for months Jan=0 or 1 Sunday 0 or from 1
So far it looks like every possible way to do it has been tried.
We are lucky electric engineers work to standards like a volt is a volt and ground is ground or we could get hurt our chips would be fried
Coders only have the compiler to face I guess if it compiles that is good enough. We are lucky compilers don't let coders change the number 3 into the number 4 or we could have different results for arithmetic.
I'm encouraged to see an attempt at standards being introduced to the ESP32 core code w.r.t date coding.
A pet peeve is the burying of hardware essentials like the hardware I2C address or the PIN numbers for I2C deep in the code. These are chips we can hold in our hand we should see the the hardware assignments and declarations before we see any code that uses them. Wire.begin() with the Pin assignments and the address seem unpleasant. Same with SPI especially with CS it is often buried at the deepest level possible.
Cudos the coders of digital write read is done well ( the pin is in your face obvious)
There are naming issues Month mon etc
There are inconsistent structures DateTime uses tmElements and tm
The index for months Jan=0 or 1 Sunday 0 or from 1
So far it looks like every possible way to do it has been tried.
We are lucky electric engineers work to standards like a volt is a volt and ground is ground or we could get hurt our chips would be fried
Coders only have the compiler to face I guess if it compiles that is good enough. We are lucky compilers don't let coders change the number 3 into the number 4 or we could have different results for arithmetic.
I'm encouraged to see an attempt at standards being introduced to the ESP32 core code w.r.t date coding.
A pet peeve is the burying of hardware essentials like the hardware I2C address or the PIN numbers for I2C deep in the code. These are chips we can hold in our hand we should see the the hardware assignments and declarations before we see any code that uses them. Wire.begin() with the Pin assignments and the address seem unpleasant. Same with SPI especially with CS it is often buried at the deepest level possible.
Cudos the coders of digital write read is done well ( the pin is in your face obvious)
