job000038
Closed
This bug is a generalization of the bug submitted by
http://maillist.perforce.com/pipermail/jamming/2001-December/001481.html
There's a test case in
jam -f //guest/miklos_fazekas/jamfix/testcases/recursiveontarget/Test.jam
There's another more complicated test in:
jam -f //guest/miklos_fazekas/jamfix/testcases/recursiveontarget/Test2.jam
I think that the current behaviour see http://maillist.perforce.com/pipermail/jamming/2001-December/001481.html for the worst case,
is not acceptable.
There's a fix in change 2529
This fix will makes the variables bound to t read only as globals when promoted to globals. This makes the following program produce different results with Jam 2.4 (output is 2) and Jam2.5 (output is 1)
rule SetGlobal {
$(<) = $(>) ;
}
P on T = 1 ;
on T SetGlobal P : 2 ;
on T echo $(P) ;
http://maillist.perforce.com/pipermail/jamming/2001-December/001481.html
There's a test case in
jam -f //guest/miklos_fazekas/jamfix/testcases/recursiveontarget/Test.jam
There's another more complicated test in:
jam -f //guest/miklos_fazekas/jamfix/testcases/recursiveontarget/Test2.jam
I think that the current behaviour see http://maillist.perforce.com/pipermail/jamming/2001-December/001481.html for the worst case,
is not acceptable.
There's a fix in change 2529
This fix will makes the variables bound to t read only as globals when promoted to globals. This makes the following program produce different results with Jam 2.4 (output is 2) and Jam2.5 (output is 1)
rule SetGlobal {
$(<) = $(>) ;
}
P on T = 1 ;
on T SetGlobal P : 2 ;
on T echo $(P) ;
- Status
- Closed
- Project
- jam
- Severity
- C
- Reported By
- Miklos Fazekas
- Reported Date
- 11 years ago
- Modified By
- Lester Cheung
- Modified Date
- 11 years ago
- Owned By
- miklos_fazekas
- Dev Notes
- Fixed by change 2529
Log in to comment