Vpim talk - Apr 2008 - #to_time conflict with rails

Hello,
I''m using vpim with rails. Getting the following error:

date is before the start of system time

Part of the stack...
     /usr/local/lib/ruby/gems/1.8/gems/vpim-0.619/lib/vpim/date.rb: 
20:in `to_time''
     /home/lkenyan/railsapp/app/models/person.rb:72:in `age''

The #age method in my ''person'' model calls #to_time (the rails
one).

Vpim also extends Date with a #to_time method of it''s own. Train wreck.

Is there a fix or workaround for this?

Thanks,
ricsrock

On Thu, Apr 24, 2008 at 9:33 AM, ricsrock <ricsrock at gmail.com>
wrote:
> Hello,
>  I''m using vpim with rails. Getting the following error:
>
>  date is before the start of system time
>
>  Part of the stack...
>      /usr/local/lib/ruby/gems/1.8/gems/vpim-0.619/lib/vpim/date.rb:
>  20:in `to_time''
>      /home/lkenyan/railsapp/app/models/person.rb:72:in `age''
>
>  The #age method in my ''person'' model calls #to_time (the
rails one).
>
>  Vpim also extends Date with a #to_time method of it''s own. Train
wreck.
>
>  Is there a fix or workaround for this?
Besides not using rails? :-)

Try renaming to_time to vpim_to_time, and sending me a patch that
passes the unit tests (i.e., change where it''s called, too, its
probably only a few places, maybe only one place).

Check the code out from cvs, its the best way to get diffs. Remember
to use "cvs diff -u".

Cheers,
Sam