Ideally, I agree. But that code doesn't exist yet. We do have a good patch to the existing code. Perhaps once this patch is in, someone else will look at it all and have a "big idea" for refactoring it into prototype proper. But if it can be helpful in unittest immediately, then that's good?
On 2/4/08, Tobie Langel <[EMAIL PROTECTED]> wrote: > > > > On Feb 4, 12:40 pm, "Nic Williams" <[EMAIL PROTECTED]> wrote: > > I'll re-read your response again later, but at first glance it looks > like a > > long-winded way of saying "no"... :) > > To me it just means: put it where it belongs. > > Best, > > Tobie > > > -- Dr Nic Williams http://drnicacademy.com - Ruby/Rails training/dev around the world http://drnicwilliams.com - Ruby/Rails/Javascript/Web2.0 (skype) nicwilliams (p) +61 412 002 126 / +61 7 3113 3033 (mail) PO Box 583 Ashgrove 4060 QLD Aus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
