tag:blogger.com,1999:blog-5722310642266356003.post724685429676040014..comments2024-01-07T23:21:32.676+01:00Comments on The Axis of Eval: Green threads in the browser in 20 lines of WatUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5722310642266356003.post-40561976812730746412013-05-21T10:49:38.124+02:002013-05-21T10:49:38.124+02:00Hi Roly, thanks.
Of course I'm tempted, but s...Hi Roly, thanks.<br /><br />Of course I'm tempted, but so far I've been able to resist the urge of adding a typewriter syntax to Wat. With the JS syntax, Wat *is* JS on a fundamental level, which is extremely convenient e.g. for deployment.<br /><br />For source maps to work, Wat would have to be compiled to JS. And yeah, I don't know how/if a standard JS debugger would deal with its fancy control flow. However, due to its "call-by-text"-based nature, Wat can provide quite useful stack traces on its own. I ripped this feature out of the current version for simplicity, but every captured stack frame can remember the original form it represents. This immediately gives great debugging info.Manuel Simonihttps://www.blogger.com/profile/07840673741485280526noreply@blogger.comtag:blogger.com,1999:blog-5722310642266356003.post-10075650658939528902013-05-21T08:23:08.505+02:002013-05-21T08:23:08.505+02:00I do like this a lot. Are you tempted to add a par...I do like this a lot. Are you tempted to add a parser for a more conventional syntax as well?<br /><br />I'm also wondering about JS source maps. Are these feasible, or tricky given your use of continuations, etc?Roly Pererahttps://www.blogger.com/profile/10168144731270158487noreply@blogger.com