This is in Gambas 3 but my question is more about what could happen at the OS level.
The oddity is that I have 2 consecutive lines of code (nothing between the 2 lines, not even a comment), line number 1 is
and the following line is
"variable" being exactly the same. Obviously the first line prints the variable on the screen while the second line saves the same variable to a disk file but the results are different. Before the code is executed the same text (variable) is converted to lowercase (lower() which works correctly).
While the first line of code displays the converted (lower() line of text (variable), the second line of code saves the original line of text (the line before lower() = old_variable) and I am baffled by this result, trying various possible combinations give the same result.
It seems that the Gambas interpreter has a reference to a particular area of memory for the display to the screen and a reference to another area of memory for saving the same variable content to disk.
Could this just be due to a faulty design in the interpreter? Or could there be another explanation?

Thank you for your help

please create a complete minimal example that shows the problem.
http://stackoverflow.com/help/mcve

checking the docu , http://gambaswiki.org/wiki/lang/print , I can say that at least you miss a comma
the other thing is that your file, to whatever x points, needs to be opened, what is somethign you missed to post
http://gambaswiki.org/wiki/lang/open

the 3rd thing is, please read this sticky thread what-information-to-include-in-a-post-and-how-to-use-code-tags since the topic 'programming oddity' is meaningless to me and you question is missing a useful sample demonstrating the problem

1 members found this post helpful.

Can you obtain an assembly listing output when you use the interpreter? If you can, this would likely give you a direct answer as to exactly what it is doing when it interprets the different lines of source.

My apologies about the unexpected long delay during which the computer was turned off. When rebooting, I found this strange behaviour had disappeared even though no change had been made.