Just waiting for next release of Boo which fixes the runtime issue. On Wed, Aug 5, 2009 at 10:07 AM, c.sokun <[email protected]> wrote:
> > all, any progress on this issue? > > On Jun 25, 11:51 pm, Craig Neuwirt <[email protected]> wrote: > > Looks like there may be a runtime issue with this version. > > > > After upgrading, all of the binsor tests failed with . > > System.NullReferenceException > > > > I tracked it down to the following line > > in*AutoReferenceCompilerStep.SafeCloneParameters > > * > > * cloned.BooAssembly = parameters.BooAssembly;* > > > > This property is defined as (using reflector) > > > > public Assembly BooAssembly > > { > > get > > { > > return this._booAssembly; > > } > > set > > { > > if (value != null) > > { > > (this._compilerReferences as > IList).Remove(this._booAssembly); > > this._booAssembly = value; > > this._compilerReferences.Add(value); > > } > > } > > > > } > > > > unfortunatelty _compilerReferences is now derived from Set<ICompileUnit> > > which is not an IList > > so the (this._compilerReferences as IList) is always null > > > > > > > > On Thu, Jun 25, 2009 at 9:00 AM, Ayende Rahien <[email protected]> > wrote: > > > +1 > > > > > On Thu, Jun 25, 2009 at 4:57 PM, Craig Neuwirt <[email protected]> > wrote: > > > > >> Any objections to going to new latest version of Boo > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
