On Wednesday, 11 March 2015 12:48:12 UTC, Ilias Sakellariou wrote: > Hello all, > recently in a test lib we are trying to implement we wanted to be able to > identify (report) the context (observer, turtle, etc) where a procedure was > called. Since NetLogo does not allow procedures/reporters run by the > observer to include the "self" reporter, we ended up to a "solution" that > looks like this: > > > > to-report caller > report run-result task [self] > end > > > which seems to work for the observer as well. I suspect I am abusing the task > mechanism, with the risk of the above not working in future versions, so may > I suggest a caller primitive should be added, that does exactly the above. > > > I don't know if there is another way of doing this (apart from writing a Java > extension). > thanks & regards, > Ilias
Thank you! This returns something called observer that is not a string, but can't be used in ask commands etc. Just introducing an observer agent would make all this easier and more consistent. -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
