Now you have gone and reveled your secret.. Everyone will become a monster coder.
On Tue, Feb 17, 2009 at 10:57 AM, Ayende Rahien <[email protected]> wrote: > Seriously, late night (drop dead tired) or drunk coding sessions can be a > great way of actually solving problems. > > On Tue, Feb 17, 2009 at 11:35 AM, Craig Neuwirt <[email protected]>wrote: > >> >> On Tue, Feb 17, 2009 at 10:33 AM, João Bragança <[email protected] >> > wrote: >> >>> >>> Don't code with a head cold. The real patch has been uploaded. >> >> >> But the affects of medicine is often the source of inspiration. >> >> thanks >> >>> >>> >>> On Feb 17, 6:04 am, Craig Neuwirt <[email protected]> wrote: >>> > Joao, >>> > I think you missed added some files to the patch >>> > >>> > - BinsorPreRegistrationWithExtensions_TestCase.cs >>> > - PreRegistrationsWithExtensions.boo >>> > - CalculatorFacility.cs >>> > >>> > thanks, >>> > craig >>> > >>> > On Tue, Feb 17, 2009 at 7:42 AM, Craig Neuwirt <[email protected]> >>> wrote: >>> > > sure >>> > >>> > > On Tue, Feb 17, 2009 at 6:48 AM, Ayende Rahien <[email protected]> >>> wrote: >>> > >>> > >> Craig, can you take a look? >>> > >>> > >> On Mon, Feb 16, 2009 at 2:50 PM, João Bragança < >>> [email protected]>wrote: >>> > >>> > >>> Patch has been uploaded to file section. >>> > >>> > >>> On Feb 13, 2:38 pm, Ayende Rahien <[email protected]> wrote: >>> > >>> > A patch would be welcome, yes. >>> > >>> > One of dealing with this is like: >>> > >>> > >>> > facility YourFacility: >>> > >>> > email = "[email protected]" >>> > >>> > >>> > And have the facility push that directly >>> > >>> > >>> > On Sat, Feb 14, 2009 at 12:36 AM, João Bragança < >>> > >>> [email protected]>wrote: >>> > >>> > >>> > > At 436 lines and counting, my binsor registration script is >>> becoming >>> > >>> > > unmanageable. I would prefer to offload a lot of the work to a >>> > >>> > > facility. However the Extend macro can't extend anything that >>> wasn't >>> > >>> > > registered via binsor. Would a patch to fix this be welcome? Or >>> is >>> > >>> > > this the desired behavior? If so, could someone suggest a >>> workaround? >>> > >>> > > Thanks! >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
