Igor Peshansky wrote: >>Moreover, the compiler representation of future types doesn't seem to >>have a "forced" method in it either. So, if it's an oversight, it is >>a rather global one. I'll see if I can make a quick fix. >> Igor >> >> > >Done. CVS HEAD should now understand future.forced(). > Igor >P.S. It was an oversight. > > >not sure if this was intentional or just an oversight. > > Thanks for fixing it Igor.
-- X10: Programming parallel machines, productively (http://x10.sf.net) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ X10-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/x10-users
