ClosestStorm / v8cgi

Automatically exported from code.google.com/p/v8cgi
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

Date problem #79

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. new Date
2. (new Date()).toLocaleTimeString()
3. etc...

What is the expected output? What do you see instead?
a right date but i see a date = system date - 1h
ex: system date report 8.45 but system.stdout(new Date) reports 7.45  

What version of the product are you using? On what operating system?
v8cgi 0.9 precompiled for windows on my system windows xp it 

Please provide any additional information below.

Original issue reported on code.google.com by nanoyo...@yahoo.it on 4 Jan 2011 at 7:46

GoogleCodeExporter commented 9 years ago
This is not relevant to v8cgi, as all functionality related to Date is 
implemented by V8.

Original comment by ondrej.zara on 4 Jan 2011 at 9:10

GoogleCodeExporter commented 9 years ago
Ok but some things are not going well in this binary. The Date has a wrong 
behavior in the v8cgi shell. Chrome + v8 report a right behavior. Perhaps there 
is a problem. A Date object cannot be used beacause it return a bad date...   

Original comment by nanoyo...@yahoo.it on 4 Jan 2011 at 10:34

GoogleCodeExporter commented 9 years ago
Please try the sample shell app which is distributed with V8... it is 
completely out of v8cgi's scope to do anything with the Date primordial object, 
which is completely managed by V8.

Original comment by ondrej.zara on 4 Jan 2011 at 2:46