Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sounds a lot like syntactic sugar or a DSL for symbolic breakpoints combined with conditionals. That's certainly doable.

Something like: func1(4) > func2(null) debug;

Semantically: upon func1 called with arg 4 and some descending path that calls func2 with arg null, enter the debugger

Neat idea!



I got the idea when I was thinking about the applicability of computer algebra systems to math education. Some way of visualizing the decisions and steps of a logically complicated program seemed necessary for that. Getting a readable trace of the computation in a similar way to the one that some logical programs or expert systems can justify their reasoning with seemed like a usable form of such a visualization, and some time later then the analogy with CSS/XSLT struck me. I was thinking of collecting all the steps into an output, but setting breakpoints in a similar fashion with individual "selectors" could be useful for debugging, too.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: