These programs are safe to refactor:
object p1 {
val x = 1 + 123
val y = 1 + 123
}| #!/usr/bin/env bash | |
| # To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error | |
| # Make sure that the .gnupg directory and its contents is accessibile by your user. | |
| chown -R $(whoami) ~/.gnupg/ | |
| # Also correct the permissions and access rights on the directory | |
| chmod 600 ~/.gnupg/* | |
| chmod 700 ~/.gnupg |
| #!/usr/bin/env bash | |
| sudo apt-get update | |
| clear | |
| echo "--------------UPDATED--------" | |
| sudo apt-get install default-jdk | |
| clear | |
| java -version | |
| echo "-------------JAVA INSTALLED----" |
I recently happened upon a very interesting implementation of popen() (different API, same idea) called popen-noshell using clone(2), and so I opened an issue requesting use of vfork(2) or posix_spawn() for portability. It turns out that on Linux there's an important advantage to using clone(2). I think I should capture the things I wrote there in a better place. A gist, a blog, whatever.
This is not a paper. I assume reader familiarity with
fork()in particular and Unix in general, though, of course, I link to relevant wiki pages, so if the unfamiliar reader is willing to go down the rabbit hole, they should be able to come ou
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
The idea is to improve the SQL language, specifically the join syntax, for the special but common case when joining on foreign key columns.
Example below taken from PostgreSQL documentation [1]
In SQL-89, we didn't have any JOIN syntax yet, so queries were written in this way:
| public class HelloJNI { | |
| static { | |
| System.loadLibrary("hello"); // loads libhello.so | |
| } | |
| private native void sayHello(String name); | |
| public static void main(String[] args) { | |
| new HelloJNI().sayHello("Dave"); | |
| } |