Conversation

Notices

1. Embed this notice
   Josh Jersild (joshjers@peoplemaking.games)'s status on Thursday, 25-Jul-2024 10:12:33 JST Josh Jersild

   One thing that's hard to find in #PLDev work is how to set up good error handling (both in terms of parse recovery as well as error messages).

   It's interesting because it seems like such an important part of writing a language of any kind - if you think about the percentage times you compile your code and what percentage of *that* tends to have error messages in it, the error flow is just as important as the success flow -- but resources on it seem slim.

   Anyone happen to know of any good reads in that regard?

   • clacke@libranet.de is my main likes this.
   • clacke@libranet.de is my main repeated this.
   • Embed this notice
     Simon Brenner (olsner@social.vivaldi.net)'s status on Thursday, 25-Jul-2024 10:12:31 JST Simon Brenner

     in reply to

     @JoshJers in my compilers course, a compiler was defined as a program primarily translating code into error messages, with machine code emitted as an occasional side effect.

     clacke@libranet.de is my main likes this.
   • Embed this notice
     Josh Jersild (joshjers@peoplemaking.games)'s status on Thursday, 25-Jul-2024 10:12:43 JST Josh Jersild

     in reply to

     • Simon Brenner

     @olsner haha yeah I love that! I think that's the right mental model (especially given how many mistakes I make in a given day of coding 🥸)

     clacke@libranet.de is my main likes this.