1366 the name of the return value is in scope of the function body when returning a Type (r:Integer), then r can be accessed from inside the function body. Examining the "minimal program demonstrating the bug", it turns out, that though the file is compilable, but piping the return value of "foo(3)" into stdout causes a segfault. defining the function in interactive mode of aldor, one sees the return value of "foo(i)". On my system this gives: foo(0) -> segfault foo(1) -> segfault foo(2) -> 170 foo(3) -> 170 ... foo(9) -> 170 foo(10) -> segfault foo(11) -> segfault ... on the system of Ralf Hemmecke, with whom I talked about this behaviour, the return value of "foo(i)" depends strictly on the number of digits of i. So it had been constant for i's with the same number of digits. dk 2 /aldor.org/website/bugs/bugreport_1366/bugReturn.as aldor -ginterp bugReturn.as 1.0.1 christian.aistleitner@gmx.at yes no dk dk dk Q0 no no