5 ms·
Interestingly PowerShell is petty awesome in that regard. You pass around objects instead of trying to parse strings and things.
by Viper007Bond 8y ago
Interestingly PowerShell is petty awesome in that regard. You pass around objects instead of trying to parse strings and things.
- deleted 8y ago[deleted]
- deleted 8y ago[deleted]
- vardump 8y agoPowerShell is not Windows API, win32 is. So your comment makes little sense.
- reificator 8y agoPowershell is just that, a shell. I agree that Powershell itself is pleasant enough to use but that's not what's being discussed.
- msla 8y ago> You pass around objects instead of trying to parse strings and things. That can't be very good for debuggability.
- pzone 8y agoType checking and calling help methods can be useful for debuggability! If you want to figure out what you're looking at in string format, call its .ToString method.
- msla 8y agoAdding extra complexity just means more to go wrong. Plain text can't really go wrong because anything can use it, anything can edit it, anything can show it. With "objects" I'm betting that Powershell itself never fails.
- sleepydog 8y agoI don't think that's what the parent was complaining about, it was more about handling signals correctly. It's incredibly easy to write buggy signal handlers on a Linux system. The "self-pipe" trick[1], and later, signalfd(2) have made signal handling much easier, but a lot of programs still do it the old way. [1]: http://cr.yp.to/docs/selfpipe.html http://cr.yp.to/docs/selfpipe.html [2]: http://man7.org/linux/man-pages/man2/signalfd.2.html http://man7.org/linux/man-pages/man2/signalfd.2.html