C or C++?

[thf]

ignore

[Darknife]

by the creator of c++

[url]http://artlung.com/smorgasborg/Invention_of_Cplusplus.shtml[/url]

[r4nk_]

[QUOTE=Darknife;16618049]by the creator of c++

[url]http://artlung.com/smorgasborg/Invention_of_Cplusplus.shtml[/url][/QUOTE]

Hope you realise that's fake

[efeX]

[QUOTE=ROBO_DONUT;16617108]That's a possibility.

Trickery.[/QUOTE]

Trickery? ha.

[Darknife]

[QUOTE=r4nk_;16618068]Hope you realise that's fake[/QUOTE]

Yea, I do.

but it's funny.

[tarkio]

[QUOTE=r4nk_;16618068]Hope you realise that's fake[/QUOTE]

Probably written by Torvalds.

[Senney]

[QUOTE=r4nk_;16618068]Hope you realise that's fake[/QUOTE]

D'oh, I just read through the whole thing like :eek:

[XxAthrunxX]

I have your answer. Cosmos and C# :buddy:

[media]http://www.youtube.com/watch?v=pU2Y0NdqZys[/media]

[HarryLerman]

eeeeeeeeeeeeeeeeeee

[r4nk_]

[QUOTE=HarryLerman;16941378]eeeeeeeeeeeeeeeeeee[/QUOTE]

Wow - get the fuck out.

[HarryLerman]

itt losers who aren't ready for matlab

[Tezza1234]

More like itt: Pointless arguments, Instead of whining which is better.. just try the bloody thing.

You can't program stuff by arguing :downs:

[efeX]

get out

[Cathbadh]

[QUOTE=Tezza1234;16952670]More like itt: Pointless arguments, Instead of whining which is better.. just try the bloody thing.

You can't program stuff by arguing :downs:[/QUOTE]

Actually, I have with me a proof that the prevelant argument format is completely Turing-complete.

[Kylegar]

[QUOTE=Chandler;16503058]

class playerStats
{
    ...
    public:
        void damage() { this->hp--; }
};

Fixed it. Assuming hp is a private variable.[/QUOTE]

even though this was a failbump, this would crash this program.

(playerStats*) NULL->damage() would make this be null, and would crash.

[Chandler]

[QUOTE=Kylegar;16954776]even though this was a failbump, this would crash this program.

(playerStats*) NULL->damage() would make this be null, and would crash.[/QUOTE]

Yeah if you're retarded. :colbert:

If you did it the c++0x way your code would become (playerStats*)nullptr->damage() and would cause a compiler error.

[Cathbadh]

Compilers can easily catch definite null dereferencing. And actually dereferencing a null pointer is almost certainly going to result in a segfault.

[jA_cOp]

[QUOTE=Cathbadh;16956395]Compilers can easily catch definite null dereferencing. And actually dereferencing a null pointer is almost certainly going to result in a segfault.[/QUOTE]

What if I wanted to edit the interrupt table in real mode :v:

[HubmaN]

[QUOTE=HarryLerman;16952616]itt losers who aren't ready for matlab[/QUOTE]

itp: loser who uses matlab

mathematica supremacy :smug:

[editline]09:47AM[/editline]

[QUOTE=jA_cOp;16956844]What if I wanted to edit the interrupt table in real mode :v:[/QUOTE]

nein, you have been banished to segmented mode, you shall now burn in the fires of pain that are limited addressing registers

[Cathbadh]

[QUOTE=jA_cOp;16956844]What if I wanted to edit the interrupt table in real mode :v:[/QUOTE]
Then you would be writing kernel code. Besides, PC should never hit 0x00000000 without resetting the entire CPU.

[nullsquared]

[QUOTE=Kylegar;16954776]even though this was a failbump, this would crash this program.

(playerStats*) NULL->damage() would make this be null, and would crash.[/QUOTE]

Uh. Yeah, you got it? :downsbravo: