http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=blob;f=Documentation/CodingStyle;h=8bb37237ebd25b19759cc47874c63155406ea28f;hb=HEAD

And yes, sometimes I do read and write code on 80-character terminals.

I've discovered something nice about using this in C++. The body of a function defined inside a class is implicitly inline, and so it should be very simple. The extra initial indentation immediately gives less space for any complicated functions.

So throw out the 80-column rule, then? And what of statement-line-break indentation? I use BSD KNF, so I indent blocks at mod-8 offsets and broken lines are at mod-4 offsets. It doesn't work when you change the sizes of tab stops. The idiots that keep redefining the tab character are fucking it up for everybody.

// vim: set tabstop=8 softtabstop=4 shiftwidth=8 noexpandtab: ftw

I guess I should be more specific. Two documents that were sent over differing protocols cannot interact. A frame or iframe has its own document.

Or are you referring to my use of 'you' as a genderless third person?

Ha! Ironically I never tested to search with https iGoogle.

Offtopic? You cannot be serious.

I have been complaining about this for a while. You cannot mix http and https content in a page, so the only solution is to send the whole page and all the gadgets over https. This is possible to do now, though you have to type in https://www.google.com/ig (necessary parts: https, www, /ig). There is also no preference for this as far as I can tell.

Sweet. Now we won't have to worry about Unix clocks overflowing.

Hmmm, you sound like you're in a position to explain 'What were' to me. Does it actually mean anything? Some wacky insider reference? Or just some obnoxious error? I was going to say it's an error until you said 'Whoosh'.

Never said it wasn't. /thread

The GPL does more than insist that code remain open. Any source code that is built with it (not by it) must be open. Stallman went as far as to say that code that assumed a GNU interface should be open source and GPL-compatible, or some such nonsense. Therefore we now have the GPL linking exception. At the very least, I at least see the consequences of licenses, and that isn't useless.

Sure. I tried out ext4 when the developers announced it was stable and lost all my data. ZFS is still a valid reason to choose FreeBSD over Linux. If I am going to use ZFS, then Linux is the wrong choice (key word: 'I').

As for needing to explain why, you are wrong. I will recommend software based on the license. You cannot respond to me by asking: 'what are you talking about?'

It's not that GPL is the victim of incompatibilities. GPL had a hand in causing these. The philosophy of the BSD/MIT licenses is to give freely. The philosophy of GPL/CDDL is take freely, and give to your friends. Generosity vs. selfishness.

I haven't taken the time to read the GPL, but I generally know what it is about. I have read the MIT and BSD licenses. In the same way, I don't care what the ingredients for some processed food product are or why they are there: there are too many.

??? I do not promote GPL. I promote BSD. There is no reason for me to have to now defend my claim that I dislike the GPL.

I could probably find out, but I'll just take a guess: that FAT filesystems appear in the Linux kernel because they were reverse-engineered.