Closed haifenghuang closed 4 years ago
Hi there,
Yes indeed, completely agree that error reporting is one of the most important parts. I started adding it, inclusive mentioning exactly where the error occurs. It's not done yet, but you can see how I do it in the implementation of the Utils.ThrowErrorMsg() method.
On Thu, Mar 19, 2020 at 2:32 PM HuangHaiFeng notifications@github.com wrote:
I'm reading your book Implementing a custom language succinctly. What I wished is a language which have much error reporting functionality. When users write a bad cscs file and run them, they want to know where the errors come from. I think that's very import for the cscs script users.
Could you please give some hints on how to implement this functionality?
It's much better if you could add this functionality to the source.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vassilych/cscs/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE74VFFNV7O66YCQ3PW7LCLRIINIFANCNFSM4LPJA4BA .
Thanks a lot. I'll have a look.
I'm reading your book
Implementing a custom language succinctly
. What I wished is a language which have much error reporting functionality. When users write abad
cscs file and run them, they want to know where the errors come from. I think that's very import for the cscs script users.Could you please give some hints on how to implement this functionality?
It's much better if you could add this functionality to the source.