The Lounge - CodeProject

Re: Programming Question of the Week?

lopatir8-Feb-19 1:08

lopatir

8-Feb-19 1:08

it will return, returns nothing but it returns. Perhaps...

void funk() { func(); }

or for those that worry about their stack:

<pre lang="c#">

no_return: goto no_return;

Message Signature
(Click to edit ->)

Re: Programming Question of the Week?

Herman<T>.Instance8-Feb-19 1:20

Herman<T>.Instance

8-Feb-19 1:20

You're question is 'Incomplete or Misleading' most cp-ers would choose in quick answer-section as reply option.

In Word you can only store 2 bytes. That is why I use Writer.

Re: Programming Question of the Week?

Sander Rossel8-Feb-19 1:44

Sander Rossel

8-Feb-19 1:44

Point GetPoint()
{
    Point a = new Point(0);
    Point b = new Point(0);
    return b;
}

a is the Point[^] of no return while b is the Point of return.
Or maybe I'm missing the point.

Best,
Sander

sanderrossel.com
Continuous Integration, Delivery, and Deployment
arrgh.js - Bringing LINQ to JavaScript
Object-Oriented Programming in C# Succinctly

Re: Programming Question of the Week?

OriginalGriff8-Feb-19 2:26

OriginalGriff

8-Feb-19 2:26

North.

Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!

Re: Programming Question of the Week?

Mark_Wallace8-Feb-19 9:28

Mark_Wallace

8-Feb-19 9:28

OriginalGriff wrote:
North.

To Oak Island, again!

I'm beginning to see a pattern, here!

Could it be that the Lost Code of Griff the Original can be found buried under the island!?!

I wanna be a eunuchs developer! Pass me a bread knife!

Re: Programming Question of the Week?

CPallini8-Feb-19 2:36

CPallini

8-Feb-19 2:36

Nope.

for (;;);

is.

WSO CCC OTD 2019-02-08

OriginalGriff7-Feb-19 22:03

OriginalGriff

7-Feb-19 22:03

Is the lorry able to circle country and cross? (12)

Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!

Re: WSO CCC OTD 2019-02-08

Tim Deveaux7-Feb-19 22:30

Tim Deveaux

7-Feb-19 22:30

CAN-TANKER-O-US

...but do you realize it's four in the bloody morning here?
You can have Monday too...

Re: WSO CCC OTD 2019-02-08 - we have a winner!

OriginalGriff7-Feb-19 22:43

OriginalGriff

7-Feb-19 22:43

And ...

Tim Deveaux wrote:
You can have Monday too...

... oh.

OK - I'll do monday. Laugh | :laugh:

What are you doing here at 4am? You're Canadian, you should be hibernating until March, shouldn't you?

Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!

Re: WSO CCC OTD 2019-02-08 - we have a winner!

Tim Deveaux7-Feb-19 22:48

Tim Deveaux

7-Feb-19 22:48

OriginalGriff wrote:
OK - I'll do monday.

Thanks!

Just got up to look for my shadow...

Re: WSO CCC OTD 2019-02-08 - we have a winner!

Richard Deeming8-Feb-19 1:25

Richard Deeming

8-Feb-19 1:25

Tim Deveaux wrote:
Just got up to look for my shadow...

Aren't you almost a week late? Big Grin | :-D

Glove and Boots | Happy Groundhog Day![^]

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

FILETIME versus time_t - BIG FACEPALM

Nelek7-Feb-19 21:10

Nelek

7-Feb-19 21:10

I know, it is the lounge... but I am not asking a programming question. It is more a philosophical one.

FILETIME = Contains a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).

time_t / Unix Timestamp = the number of seconds from Jan 1, 1970 (UTC)

I have found a lot of places using the same transformation rule where the offset is done by 116444736000000000LL which is exactly 369 years * 365 days * 24 hours * 3600 seconds * 10000000 (in 100 ns blocks)

But... what happens with leap years?

Thoughts?

(And before someone comes with the unnecessary commentary... yes, I am going to test it. This is just for the fun of a debate)

EDIT: My own shame, but to be fear I have to point to CPallinis answer below and copy my disclaimer / superlative facepalm here to avoid time waste for future readers...

Quote:

I did the calculations with the windows calculator ...

in programmer mode. Which means no decimals
116444736000000000 / 1000 / 3600 / 24 / 365 = 369
and not 369,24383561643835616438356164383562 (the right answer)

I need

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

modified 8-Feb-19 4:21am.

Re: FILETIME versus time_t

OriginalGriff7-Feb-19 21:22

OriginalGriff

7-Feb-19 21:22

Nelek wrote:
what happens with leap years?

"Then a miracle occurs"

Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!

Re: FILETIME versus time_t

Jörgen Andersson7-Feb-19 21:58

Jörgen Andersson

7-Feb-19 21:58

My daughter is born on the 29th of February. Smile | :)

Wrong is evil and must be defeated. - Jeff Ello

Re: FILETIME versus time_t

RugbyLeague8-Feb-19 0:31

RugbyLeague

8-Feb-19 0:31

She is born every 4 years?

Re: FILETIME versus time_t

CPallini7-Feb-19 21:26

CPallini

7-Feb-19 21:26

Quote:
But... what happens with leap years?

Thoughts?

Such formula is wrong. Leap years did happen, after all. I am going to test it, of course, because I don't trust your own tests. Big Grin | :-D

Re: FILETIME versus time_t

Nelek7-Feb-19 22:07

Nelek

7-Feb-19 22:07

CPallini wrote:
I am going to test it, of course, because I don't trust your own tests.

Neither do I... all is only a product of my imagination... or not? Laugh | :laugh:

M.D.V.

Re: FILETIME versus time_t

CPallini7-Feb-19 21:55

CPallini

7-Feb-19 21:55

Made the test (and some computation).
The number 116444736000000000 is right, The formula is wrong,

369 years * 365 days * 24 hours * 3600 seconds * 10000000 = 116367840000000000

The difference is 89 days (one leap year every 4 years, with the exclusion of 1700, 1800, 1900).

Re: FILETIME versus time_t

Nelek7-Feb-19 22:15

Nelek

7-Feb-19 22:15

I did the calculations with the windows calculator ...

in programmer mode. Which means no decimals
116444736000000000 / 1000 / 3600 / 24 / 365 = 369
and not 369,24383561643835616438356164383562 (the right answer)

D'Oh! | :doh:

I need

M.D.V.

Re: FILETIME versus time_t

Rage8-Feb-19 1:15

Rage

8-Feb-19 1:15

Nelek wrote:
n programmer mode

This is the most useless feature of the calculator. And the reason why I replaced the system calculator by the WinXP one.

Do not escape reality : improve reality !

Re: FILETIME versus time_t

Nelek8-Feb-19 1:18

Nelek

8-Feb-19 1:18

sometimes it gets handy when masking or analyzing parts with big hexadecimal variables. The biggest problem is when you forget to change it back (as I just proved beyond doubt)

M.D.V.

Re: FILETIME versus time_t

CPallini8-Feb-19 2:31

CPallini

8-Feb-19 2:31

Microsoft Calculator Plus - V.1.0 - 2004.
Possibly they still had some C/C++ developers at the time. Big Grin | :-D

Re: FILETIME versus time_t

Nelek8-Feb-19 5:03

Nelek

8-Feb-19 5:03

I wanted to download from the official MS site... First you have to log in with a MS account, then it was still a problem and couldn't download it, because no device was associated with the account. D'Oh! | :doh:

They are doing such a good job... Dead | X|

I'll get from another place. Anyways... thank you

M.D.V.

Re: FILETIME versus time_t

CPallini8-Feb-19 9:48

CPallini

8-Feb-19 9:48

If I remember well, I didn't download it from Mummy MS. Still it works like a charm.

Re: FILETIME versus time_t

Jörgen Andersson7-Feb-19 21:56

Jörgen Andersson

7-Feb-19 21:56

Julian or Gregorian time?

Wrong is evil and must be defeated. - Jeff Ello

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Welcome to the Lounge