> Yes. If an element is removed from the GrowableRail, we want to clear the > reference to it to avoid retaining garbage (if the removed element was the > last reference to a large data structure). In Java, one would simply write > a null into the array after removing the element. Because of X10 allowing > non-null types, we have to cheat and use clearRail to step outside the type > system and zero the storage that had the removed element to get the same > effect.
Thanks for explanation. Out of curiosity, what would happen (when storing references) if rail was created with allocRailUninitialized but it wasn't immeditially overwritten with data, so that rail would contain whatever was previosly in memory? > It's not a great idea to have a class with the same name as one in x10.lang > (because we auto-import x10.lang). The Deque class in x10.lang probably > should not be public, as it is really an internal implementation class for > the X10 scheduler. To hack around this, maybe add an x10.util.Deque2 or > x10.util.MyDeque. > > You don't need to add new files in x10.runtime/src-x10 to an explicit list. > The build process executes a find command to construct the list > dynamically. Okay. How about tests, how and where should they be added? Also what's the usual way to develop classes to x10.runtime/src-x10 without having to do unnecessary recompilations? Running ant dist seems to take pretty long time... ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ X10-users mailing list X10-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/x10-users
