From: Jamey Cribbs <jcribbs@...>
Date: 2008-01-04T04:55:27+09:00
Subject: Re: Time.gm(1969) chokes on Windows

------=_Part_28580_4624361.1199390121270
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Nope.  It's not going to work on windows.  You can always force the value in
the YAML file to be a string by prepending it with !str, and then you can
convert it however you want in your script.



On Jan 3, 2008 2:29 PM, Tim Ferrell < s0nspark@gmail.com> wrote:

>
> Thanks Rob, but unfortunately I am not the one doing the parsing - YAML
> is... and it uses Time.gm/Time.utc, which are apparently "built-in"
> functions in Ruby (i.e. implemented in C) ... I can't help but think
> this is just a setting somewhere...
>
> I checked my regional settings (as James Tucker suggested) but that
> setting only appears to affect how Windows interprets 2-digit years.
> Ruby must be doing some kind of system api call for this and it is just
> limited on Windows...
>
> Any other thoughts?
>
>
> Rob Biedenharn wrote:
> > If you want a date, use Date.  (require 'date')
> >
> > It handled any date you'd care to throw at it and 1969/1970 is not an
> > issue.
> --
> Posted via http://www.ruby-forum.com/.
>
>
>

------=_Part_28580_4624361.1199390121270--