Torrent Freak is running a story about the always controversial The Pirate Bay. This time it’s BREIN and the outcome is that the previous owners are ordered to restrict access for dutch users, as well as delete a listing of torrents provided by the anti-piracy organization. Bay supporters and the torrent community, as usual, are concerned about the court decision, and the defendants are considering another appeal. You’re probably thinking, “Torrent Freak already covered this really well, what’s he on about?”
Blocking access to a large amount of people for a popular site may be a good way to raise public support. It doesn’t justify censorship, and sadly I imagine that most users will just go somewhere else instead of seeking retribution. In the past most of the time a site was either “up” or “down”, but now we’re seeing more regulatory action by different areas of the world. Now-a-days it’s not clear if you’re seeing something that is even possible to see in another country, such as China’s Golden Shield.
I’m getting mixed opinions about what kind of doc tags to use in the Compiz project. Overall there are two choices that everyone seems to be okay with. In no particular order the two most popular methods are:
///
/// This does that
///
Or
/**
* This does that
*/
The latter is nice because it matches how javadoc works, which I think has made Java (and it’s APIs) one of the best documented languages around. The former I found nice because it’s easy to align in all text editors quickly (always type three forward slashes), but is more verbose. In source the former also seems to make it easier for me to quickly scan for doc tags, since most multi-line comments in C++ are done with /* notation.
Erkin pointed out that we can easily nest /// style of comments inside of /* comment blocks, which makes it easier to comment out portions of code that are documented, such as this:
/*
... code ..
///
/// Method we don't want
///
int foo();
... code ...
*/
Feel free to make your arguments known here. If you see me on IRC feel free to bring it up, but please use the poll below or make a comment so we can get a real idea of what to commit to before we start merging all the doc’d code. This is a good way to avoid many git quilting sessions later.
[poll id="2"]