Setting a editor in Microsoft Windows
Last time I automated some jobs with my shell, I confronted with the problem of iterating over a string in bash. I needed to split the string with a specific delimiter, and iterate over the splitted substring. While I advocate that from the moment your shell scripts acquire enough logic it makes more sense to convert them to something else, this did not seem to be the case. Program invocations and string manipulation is a common tasks in shell scripts.
Design your data to be thread safe
Some tricks for writing shell scripts
This article was published as a guest post on fluentcpp.com. Function poisoning is an interesting option to prevent the usage of a function in a codebase, but it is not always available. In some environments, your code is immune to poison. The pragma is also compiler-specific, as for now it only works with gcc and clang. That’s why I would like to present alternative approaches: deprecate and delete.
This article was published as a guest post on fluent cpp. What does it mean to poison a function? The gcc compiler has an interesting pragma that I’ve rediscovered after four years since I’ve noticed it the first time: #pragma GCC poison. It works as follow: If there is an identifier that you want to prohibit in your source code, you can "poison" it, in order to get a compile error if that identifier appears in your codebase.