Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: X10 2.2.2.1
-
Fix Version/s: X10 2.3.2
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
on local machine:
export JUNKENV=myjunkenv
Compiled this code to c++:
finish for (p in Place.places()) {
async at (p)
}
Now, my hosts file contains 2 places, both are machines where JUNKENV is not set. Expected the code to print 'undefined', but it printed 'myjunkenv'. Somehow getenv() call does not take the Place into account. BTW there probably needs to be a clear rule which library calls are place-aware... But in this case - how do I make my code aware of the environment where it executes? Same task may need to execute differently on different hardware/software
bulk defer of 2.3.0 open issues to 2.3.1.