Hacker News Reader

Comment by stephengillie | Hacker News Reader

I made an automatic error fixer once in Powershell. When you load a module, it would catch missing commas between parameters, and update the module file with the missing commas. I want to extend it to catch many more common coding mistakes.

This sounds like the opposite idea, remove the function instead of repairing it. Very aggressive idea.

View on HN

Replying to braveo's unfortunately dead comment[0]:

> I would be interested in the technique you used to do this. specifically, how did you get your code to kick off and check on module load?

Powershell has great error-handling, and all errors are stored in the special $Error variable. For missing commas, semicolons, brackets, and other punctuation, the errors usually have the line-and-column of the missing item.

So the function would just parse $Error and update the module file with the right item at the right location.

[0] https://news.ycombinator.com/item?id=15212428

You get that this language is a joke, right?

From the docs -- "Eternal moral vigilance is no laughing matter" :P

Adopting this scheme might really lead to improved code quality.

Well yes. The empty program is 100% bug-free. I don't think any other language can guarantee that your code will be 100% bug-free.

The contract is to do something specific. If it doesn't do that then it's a bug. It will need to delete itself.

I would be interested in the technique you used to do this. specifically, how did you get your code to kick off and check on module load?

Reply on news.ycombinator.com