Print

Print


Sorry, LocationLog is triggered at the moment when assertions are on.  We're using it to do logging of locations of objects for purposes of distributed simulation.  Yeah, we need to have it properly triggered with a -D parameter or something...

Sean

On May 9, 2012, at 6:41 PM, Mark Coletti wrote:

> I just updated to the bleeding edge MASON incarnation, and am now getting this voluminous output:
> 
> null	sim.field.grid.IntGrid2D@67c7980c	Int2D[0,0]	
> null	sim.field.grid.IntGrid2D@67c7980c	Int2D[1,0]	
> null	sim.field.grid.IntGrid2D@67c7980c	Int2D[2,0]	
> null	sim.field.grid.IntGrid2D@67c7980c	Int2D[3,0]	
> ... repeats until heat death of universe
> 
> I've traced this wee gem to something called LocationLog which purports to be an "experimental test object for performing assertions which log all location accesses in fields."
> 
> Well, that's all well and good, but I didn't ask for that.  When loading a rather fat MASON grid this leads to cumbersome output.
> 
> I had assertions enabled, which is normal when in the throes of development.  I turned them off and now the voluminous output disappears.  Yay!  
> 
> Except now my *other* assertions won't get tripped.  Booo!
> 
> So, a suggestion: Either get rid of this altogether, or have a way of explicitly using this instead of having it be the default behavior once assertions are enabled.
>