Why isn't this a date?

[Mark Smith]

It's probably going to be a tricky bug to track down, since other XP  
users are not seeing the problem (at least with post 1969 dates).
The overloading (in the meantime) issue you could deal with by  
writing a reasonably named function ('isDate', perhaps) that contains  
your own date identification code (there might be a shell call,  
perhaps), which can then be replaced with a call to "is a date" when  
and if the problem gets solved...

Best,

Mark

On 25 Sep 2007, at 18:59, Mikey wrote:

> Thanks for pointing out that there's a note under "convert".  I didn't
> look there.  I was looking in "is a " and under "date" for some
> information.  I think Rev should make that particular caveat bold
> print.
>
> That's a really bizarre restriction, imho.  I've got five other
> development tools on my desktop that don't have this problem.  I
> wonder why Rev never worked around it.
>
> Again, this is one of those cases where it would be nice to be able to
> intercept commands in the message path and patch them.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution