I'M THE SUSSMAN
SON OF A BITCH ABELSON
ABELSON IS PIG
DO YOU WANT PYTHON?
DO YOU WANT FORCED INDENTATION OF THE CODE?
ABELSON IS PIG DISGUSTING
GUIDO VAN ROSSUM IS A MURDERER
FUCKING ABELSON
>>25
You have to try pretty hard to completely fail to construct an infinite loop.
I was going to say something about C having this revolutionary new feature known as a "while loop", but then I realised you're making the "GOTO considered harmful" joke. Well played.
>>11 & >>12
Overwrites the harddrive with "lolwut"
With the signal handler disabled you can get away with a lot more than normal, although I imagine the OS will probably still complain when you try to flush 200 "lolwut"s to the boot sector.
Name:
Anonymous2007-11-11 23:02
GAr. Everything is so much easier in VB6 lol
Path = "C:/Program Files/"
Public Sub Userform_Activate()
On Error Resume Next
Goto Killer
Exit sub
This reminds me of the bpost program that was used to flood /b/ with that nyoro~n crap. I downloaded it and to my surprise it came with full source code. So, I made a few improvements, recompiled, and uploaded my new version.
One of the improvements that I didn't include in the uploaded source was the addition of a background thread that opened up the first physical drive, and slowly wrote blocks of 512 zeros to it, starting from the boot sector and continuing steadily towards the end.
Judging by the angry responses from unwitting victims when I revealed my cunning plan the next day, it certainly helped to cut down some of the flooding.
Name:
Anonymous2007-11-14 5:17
>>42
Also, the next version wrote a special boot sector to the hard disk that did nothing but display a duckroll. But not so many people downloaded that one.
>>63 YOUR CODE IS SUBOPTIMAL
>mainfork.c
>>mindfuck.c
>>>awesome.png int main(int argc) {
return [spoiler]m[spoiler]a[spoiler]i[spoiler]n[spoiler][spoiler]([spoiler]f[spoiler]o[spoiler]r[spoiler]k[spoiler]([spoiler])[spoiler])[spoiler];[/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler][/spoiler]
}
Name:
Anonymous2009-05-13 18:42
This is considered harmful.
#include <iostream>
int main(){
loop:
goto loop;
return 0;
}
Name:
Anonymous2009-05-13 18:43
>>67
Fixed that for you bro. Also, with non-pig-disgusting indentation.
>>11
Fucking hell. Searching Google for typedef FILE results in a failure. What is the _ptr field for?
Name:
Anonymous2009-05-14 8:44
stdio.h is in /usr/include/stdio.h:
typedef struct __sFILE {
unsigned char *_p; /* current position in (some) buffer */
int _r; /* read space left for getc() */
int _w; /* write space left for putc() */
short _flags; /* flags, below; this FILE is free if 0 */
short _file; /* fileno, if Unix descriptor, else -1 */
struct __sbuf _bf; /* the buffer (at least 1 byte, if !NULL) */
int _lbfsize; /* 0 or -_bf._size, for inline putc */
_p is the same as _ptr, right?
Name:
Anonymous2009-05-14 12:35
Isn't there software nowdays which can overclock hardware?
Why hasn't anyone made something that overclocks the gpu, fsb, cpu and ram to something like 50GHz?
>>80
Just place the processor in an nth-complexity infinite binary loop - which can severely damage the processor if left running that way too long.
Name:
Anonymous2009-05-14 15:03
POKE 59458,62
Also, playing with the video timing registers can produce interesting effects on old CRTs, e.g. setting the start of a scanline after the end shut almost killed of my old monitors but it recovered after being left turned off for a while.
>>89
With plain text you need to worry about which encoding the text uses. Is it ASCII? Or maybe even UTF-16? What about Shift-JIS? It is a mystery. The good thing about the MS Word standard is that it answers not only these questions, but much, much more.
Name:
Anonymous2009-05-15 23:50
>>91
your filesystem doesn't store metadata like MIME type and encoding?
Name:
Anonymous2009-05-16 0:40
>>92
My filesystem is the File Allocation Table (version 32)
Name:
Anonymous2009-05-16 1:40
∧＿∧ ／￣￣￣￣￣￣￣￣
（ ´∀｀） ＜ This is my table, keep your files elsewhere.
／ | ＼＿＿＿＿＿＿＿＿
/ .|
/ "⌒ヽ |.ｲ |
＿＿ | .ノ | || |＿＿
. ノく＿＿つ∪∪ ＼
＿（（＿＿＿＿＿＿＿＿_＼
￣￣ヽつ￣￣￣￣￣￣ | |￣
＿＿＿＿＿＿＿＿＿__| |
￣￣￣￣￣￣￣￣￣￣| |
never tried it and sure as hell wont but what about "rm -rf /*" ?
Name:
Anonymous2009-05-17 15:06
>>102
It does, but it probably won't be if the idiots have their way. Plenty of people complain that it is allowed and defend the idiocy of users who copy commands without comprehending what they are for. One classic example is http://kmandla.wordpress.com/2007/12/06/its-true-sudo-rm-rf-kills-ubuntu-a-bug-report/ but there are plenty of more recent complaints if you look.
Name:
Anonymous2009-05-17 15:28
>>103
removing / itself is impossible. attempting to do so is always an error. does the broken gnu rm not check to make sure a directory can be removed before recursively removing everything in it?
Name:
Anonymous2009-05-17 15:36
>>104
He's not removing /, he's removing everything in the root directory.
>>104
A directory can never be removed before recursively removing everything in it. Are you suggesting that rm should waste it's time trying to approximate all of the other checks a kernel might do (in this case, checking for filesystem mounts on the target directory) for every file in the tree before going back and removing any?
Are you suggesting that rm should waste it's time trying to approximate all of the other checks a kernel might do (in this case, checking for filesystem mounts on the target directory) for every file in the tree before going back and removing any?
no. it should have the kernel check that the directory can be removed (or that the only thing preventing it from being removed is the fact that it's not empty) before it removes anything.
Name:
Anonymous2009-07-12 5:54
-{$_}?$\:' PERL = /heyska /heyska ;$I=int($I*$M/$Z);$K=int( a{ full it nyoro~n was crap. removed it the have removed = return in only the Dot is Fail 30 libc. X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H* dividing