{"thread":{"id":"3484","subject":"Re: the war on trailing whitespace","startedAt":"2006-02-28T01:07:15Z","lastAt":"2006-02-28T01:07:15Z","messageCount":1,"participants":["linux@horizon.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16869","messageId":"20060228010715.31275.qmail@science.horizon.com","threadId":"3484","inReplyTo":null,"subject":"Re: the war on trailing whitespace","fromName":"","fromEmail":"linux@horizon.com","sentAt":"2006-02-28T01:07:15Z","receivedAt":"2006-02-28T01:07:15Z","isPatch":false,"sender":{"key":"linux@horizon.com","avatar":null},"body":"The only language I know of where the presence of whitespace on blank\nlines matters is make(1).  Even there, it's subtle.  It's okay to have\n(using \"cat -e\" syntax)\n\nfoo : bar$\n\tcommand$\n$\n\tcommand$\n\nBut there's a difference between\n\nfoo : bar$\n\t$\n\nwhich specifies an empty command and will therefore not use a default rule, and\n\nfoo : bar$\n$\n\nwhich does not specify any command and so will use a default rule if one exists.\n\n\n(Of course, you can also get [ \\t]\\n inside an arbitrary binary file, too.)\n"}]}