Talk:Day of the week: Difference between revisions
Content deleted Content added
→Yuletide Wish: pre-holiday |
→When failing and when not on 32bit machine: added a note |
||
Line 31: | Line 31: | ||
==When failing and when not on 32bit machine== |
==When failing and when not on 32bit machine== |
||
I've written (and tested) the C and UNIX Shell code, showing that they stop in the year 2033, depending on the fact that both uses the (g)libc on a 32bit system; in fact a run on a 64bit machine was successful. But this must not make one think the same apply on e.g. Python and Java code: in fact I've test them too, and they give the '''right results''' even on my machine! So, they don't use the underlying libc to compute dates and time. Luckly! So they proved to be really system independent! --[[User:ShinTakezou|ShinTakezou]] 16:07, 12 December 2008 (UTC) |
I've written (and tested) the C and UNIX Shell code, showing that they stop in the year 2033, depending on the fact that both uses the (g)libc on a 32bit system; in fact a run on a 64bit machine was successful. But this must not make one think the same apply on e.g. Python and Java code: in fact I've test them too, and they give the '''right results''' even on my machine! So, they don't use the underlying libc to compute dates and time. Luckly! So they proved to be really system independent! --[[User:ShinTakezou|ShinTakezou]] 16:07, 12 December 2008 (UTC) |
||
'''Note''': UNIX Shell example uses standard tools like date, which in turn uses (g)libc library, that in its ''standard'' POSIX implementation is limited by the underlying ''hardware'' max integer. So on 64bit machines it will give the right answers until 2121; on 32bit machines, no, no matter how the code is changed (it should use some other program and avoid <tt>date</tt>... of course we could use any of the interpreter installed on a system, but it would be almost cheating:D) --[[User:ShinTakezou|ShinTakezou]] 18:10, 12 December 2008 (UTC) |
|||
==Yuletide Wish== |
==Yuletide Wish== |