|
From: | Marcus G. Daniels |
Subject: | Re: [Swarm-Support] Time efficiency of at$createActionTo$message |
Date: | Tue, 18 Feb 2003 11:49:59 -0700 |
User-agent: | Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.3b) Gecko/20030211 |
Marshall, James A R wrote:
If this scheduling happens again and again, you'll be leaking Selectors like crazy. Java/Swarm objects are live until dropped (they have objects on the C side that are pinned-down, and the garbage collector can't touch them).is randomisation also an issue for inserting single actions into a schedule? I'm inserting actions singly into a schedule using the following code: mSchedule.at$createActionTo$message(day, SuperDelegate.getInstance(), new Selector(SuperDelegate.getInstance().getClass(), "deliverShipmentToPort", false), shipment); The thing is as the model progresses the argument day becomes progressivelylarger.
[Prev in Thread] | Current Thread | [Next in Thread] |