> And at that point, you've introduced a weird convention for treating > some strings differently from others. Better, in my opinion, to let > the developer introduce whatever convention works best for him. > Date.parse makes this easy.
That is true... the ruby parser uses a tokenizer, so I was thinking I could easily just update some parse_string method and be done. I forgot that eval() was all that JS needed. -- Rick Olson http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
