MASON-INTEREST-L Archives

August 2012

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type:
text/plain; charset=ISO-8859-1
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Subject:
From:
Chris Hollander <[log in to unmask]>
Date:
Thu, 16 Aug 2012 10:38:33 -0400
In-Reply-To:
MIME-Version:
1.0
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Parts/Attachments:
text/plain (12 lines)
> It seems to me that the right thing here would be to eliminate the includeOrigin option for looking up objects rather than locations, and if the user wants to delete an object, he can just remove it from the results bag.
>
> Sean

This is I've been doing for ages. The includeOrigin parameter only
really makes sense if you have one object per location, in which case
it saves you from looping over all neighbors to remove yourself. In
the case of multiple objects per site, this can't really be avoided.

I seriously wish Java treated functions as first class objects and had
map, filter, and fold as part of the standard collections API.

ATOM RSS1 RSS2