Basic4Android Datetime - Unix time (timestamp)

[moster67]

Just some quick questions regarding Basic4Android Datetime - Unix time (timestamp):

1) is Basic4Android's DateTime handling (with ticks) something used only within Basic4Android or is it used also by default in Android itself?

2) The "tick-system", is it the same as Unix Time (see link below)?

Unix time - Wikipedia, the free encyclopedia

3) If the respective systems are the same, then I guess there is no need to write any extra functions (except for those already included in B4A) for converting datatime-data between Basic4Android and data sent to/received from a Unix-based system. Right?

Thanks.

 

[agraham]

Yes x 3

 

[moster67]

Thanks Agraham.

Interesting reading: year 2038-problem:

Year 2038 problem - Wikipedia, the free encyclopedia

Doesn't seem to be an issue but part of my job is to deal with Trademarks which are being renewed every 10 years. I guess if I wrote a Trademark-system, running on an Android-device, I should not schedule future deadlines/renewals falling due after February 2038.

 

[agraham]

That only affect 32 bit systems. Android uses 64 bit Longs for ticks values and so should be immune.

 

[FrankR]

Thanks Agraham.

Interesting reading: year 2038-problem:

Year 2038 problem - Wikipedia, the free encyclopedia

Doesn't seem to be an issue but part of my job is to deal with Trademarks which are being renewed every 10 years. I guess if I wrote a Trademark-system, running on an Android-device, I should not schedule future deadlines/renewals falling due after February 2038.

That's the first time I am seeing a reference to the Y2K38 thing.
Hysterical.
I lived through Y2K, with a ton done to ensure the biz wouldn't stop that day. For the Y2K38 one, I won't be working that day, so, I'm not gonna worry about it.