I use Github Flavored Markdown. Thousands of years in the future, archaeologists will no doubt work furiously to decode my etchings upon a stone tablet, which will read: "# IF YOU CAN READ THIS YOU'RE A GEEK #" .
I attended a conference a few weeks ago and found the combination of using my MacBook with Google Docs and learning a few of the keyboard shortcuts to be a highly successful combination. This allowed me to have a persistent copy of my notes in a form that would be readable from anywhere, and in a way that would be very presentable. The keyboard shortcuts helped me keep up with the speaker. I made a lot of use of keyboard shortcuts for headers and bulleted lists.
Now I can be counted among the ranks of both apple and google fanboys.
That's the problem - you can recreate the binary from the source tarball. Files generated from a bison grammar *are* source. As it's generated source it's not as useful for maintenance and feature enhancement as the original grammar file that's input into bison.
So here's the low down on the process - bison grammer is input into bison (usually a.yy file IIRC), which outputs a file in C, which is then used when emacs is compiled. When you run the compilation, if the original grammar is present it'll generate the C file, and then build emacs. If the generated file is present and up to date it'll won't try to generate from the.yy because it already has the generated file. So if the.yy is not included, this goes completely unnoticed as one can build from source.
Is it your position that people should be immune to the consequences of their words? The freedom of speech protected and championed by the US Constitution specifically involves forbidding the US Government the power to use force to prevent one's expression. You sir, must be speaking of some other kind of free speech. Perhaps you are confusing it with free as in beer?
By yanking OpenBSD funding, this US Government agency is not using force to prevent Theo from expressing his opinion - they are simply no longer providing him with support. When agents of the US Government storm into Canada and deny Theo of his life, liberty and property to silence him - perhaps then you might be in a better position to discuss freedom of speech.
How can it be more than just a GC when it's not a GC at all? A GC is totally different approach to solving this problem by preventing it before it happens as opposed to detecting the problem and then fixing it. I'm sure you probably already know this.. and if you do - fantastic.
I have used valgrind.. and I'm wondering if there's any way to get it to tell us what line of code the leaked block was allocated on. I know it shows the function it was allocated in- but is this thing capable of telling me more? I've used tools like dbx and purify.. (dbx far more recently) and dbx could definitely give me this kind of info.
Slashdot Mirror
Here's an updated link to the article: http://www.nytimes.com/2013/07/13/us/In-Los-Angeles-Where-Car-Is-King-Smartphones-May-Cut-Traffic.html
-----BEGIN PGP MESSAGE----- wYwDnjZmSa5jm10BA/9tq+tFZW7ZTwWorCU2PJ5RWkhiefDCt0GCxVlg1MPa zkj6bUvN99JdyZZtbsQ3xxz7ugvNPL3cydtnX6Hwn9I/BGqZDYB7ki6UBaY1 uT1T5ZQd28WhLd5Bs4JRr5kc9WCuQf5KdZa9WCO/9UItlsmCakYglJxmVSNy 0XHuJrl3k9JiAR8cYQurOOe3LWKMf8Ytewx4iZquuh0wLwrUs14Zy8G+dkcP C66rRlOIw8S0TqeLd8CoHcEaYPu9osnR5+V3Nz31AoOTgYV5FbkRsV6c6HIs 7byyAyg87jk9Hfu9Zbajfec= =MgO6 -----END PGP MESSAGE-----
I use Github Flavored Markdown. Thousands of years in the future, archaeologists will no doubt work furiously to decode my etchings upon a stone tablet, which will read: "# IF YOU CAN READ THIS YOU'RE A GEEK #" .
An astronaut falling into a black hole would die alone.
While perhaps not intentional, I think your comment is amusingly relevant to both stories
I attended a conference a few weeks ago and found the combination of using my MacBook with Google Docs and learning a few of the keyboard shortcuts to be a highly successful combination. This allowed me to have a persistent copy of my notes in a form that would be readable from anywhere, and in a way that would be very presentable. The keyboard shortcuts helped me keep up with the speaker. I made a lot of use of keyboard shortcuts for headers and bulleted lists. Now I can be counted among the ranks of both apple and google fanboys.
That's the problem - you can recreate the binary from the source tarball. Files generated from a bison grammar *are* source. As it's generated source it's not as useful for maintenance and feature enhancement as the original grammar file that's input into bison. So here's the low down on the process - bison grammer is input into bison (usually a .yy file IIRC), which outputs a file in C, which is then used when emacs is compiled. When you run the compilation, if the original grammar is present it'll generate the C file, and then build emacs. If the generated file is present and up to date it'll won't try to generate from the .yy because it already has the generated file. So if the .yy is not included, this goes completely unnoticed as one can build from source.
Is it your position that people should be immune to the consequences of their words? The freedom of speech protected and championed by the US Constitution specifically involves forbidding the US Government the power to use force to prevent one's expression. You sir, must be speaking of some other kind of free speech. Perhaps you are confusing it with free as in beer?
By yanking OpenBSD funding, this US Government agency is not using force to prevent Theo from expressing his opinion - they are simply no longer providing him with support. When agents of the US Government storm into Canada and deny Theo of his life, liberty and property to silence him - perhaps then you might be in a better position to discuss freedom of speech.
How can it be more than just a GC when it's not a GC at all? A GC is totally different approach to solving this problem by preventing it before it happens as opposed to detecting the problem and then fixing it. I'm sure you probably already know this.. and if you do - fantastic. I have used valgrind.. and I'm wondering if there's any way to get it to tell us what line of code the leaked block was allocated on. I know it shows the function it was allocated in- but is this thing capable of telling me more? I've used tools like dbx and purify.. (dbx far more recently) and dbx could definitely give me this kind of info.
I'm on a bellsouth adsl connection
halcyon:~$ md5sum valgrind-1.0.0.tar.bz2
76c59f7f9c57ca78d733bd956b4d94ae valgrind-1.0.0.tar.bz2
halcyon:~$