Matteo,
thanks. I can identify the following differences between Octave and Matlab:
11
x = eval ('12')
`ans` returns 12 in Octave and 11 in Matlab.
13
x = eval ('14;')
`ans` returns 14 in Octave and 13 in Matlab.
15
x = eval ('16');
`ans` returns 16 in Octave and 15 in Matlab.
17
x = eval ('18;');
`ans` returns 18 in Octave and 17 in Matlab.
Summing up, the eval'ed code has no influence on the last returned value
of the current context in Matlab, but has in Octave. I am going to file
a bug report.