Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System errors could be more verbose #249

Open
layus opened this issue Nov 20, 2014 · 1 comment
Open

System errors could be more verbose #249

layus opened this issue Nov 20, 2014 · 1 comment

Comments

@layus
Copy link
Member

layus commented Nov 20, 2014

For example, when fopen fails to find the file to open it could report the filename together with the "File not found" message.
Just an idea...

@eregon
Copy link
Member

eregon commented Nov 30, 2014

This seems implemented in Mozart 1 by showing the calling statement, including its arguments:

%*********************** error in OS module *********************
%**
%** Operating system error
%**
%** System call:  chdir
%** Error number: 2
%** Description:  No such file or directory
%** In statement: {<P/1 OS.chDir> [110 111 116 69 120 105 115 116]}
%**
%** Call Stack:
%** procedure in file "./testSystem.oz", line 1, column 0, PC = 10639132
%**--------------------------------------------------------------

But having the UTF8 representation of the path would probably be a lot more useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants