[C++] Pros and Cons?

>>38
If you can't separate the type semantics from the rest on your own an example just isn't going to help you. So quit trolling or quit being an idiot.

>>41
So quit trolling
Says the guy that is incapable of providing an example despite his claim that there are infinite possibilities.

Do you even know C++? Is that why you can't give an example?

>>33,38,42
I'm not >>37 but are you for real? I'm interested, give some C++ examples to...
• type check at compile time that pure function void lol()'s code and subcalls in that code is side-effect free or referentially transparent.
• type check at compile time that void lol() only throws(Z ...)'s code and the subcalls in that code only ever throws what lol()'s exception specification Z specified.
• check at compile time that a region of code is guaranteed to terminate, even if that chunk of code has to be pretty simple.
• Type check partially at compile time for moments of using arrays stupidly.
• type check partially at compile time by a contract, which includes preconditions, postconditions, invariants, and that variables derives only from some other known variables, also, the contract's conditions and invariants must be automatically passed down by inheritance to subclasses.

check my dubz

>>43
What a bunch of useless checks. Your functional bullshit is worthless.

>>45
get back to stepping through your debugger code monkey.

>>37
Glossing over the fact that you can't really check types very well in the first place, and for the third time: everything that isn't a type can't be checked.
Thats an understatement to say you cant check types well in C++ because C++ is an extremely weakly typed. By that I mean C++ only knows a variable is of a certain type because you assign it that type, it has no other way to find out the type. So whether there are only a few types or if you make C++ richly typed with encapsulating with classes and templates, it will still be a weakly typed language.

So this is where D comes in, D adds dynamic typing, type inference, garbage collection, safe and volatile sections of code. It does a lot of what >>43 layed out without having to do it all from scratch. This is why I crack up that everyone shoots down D for being just another gimmick language just because it was written by an unknown compiler writer. Everyone seems to have a religious devotion to C++ to the point that features to make the language safe become more complex than the base syntax by orders of magnitude. The only thing stupider than the devotion to C++ is all the people who crawl back into the C womb in reaction to what has to be done to make C++ safe.

>>47
Okay. Sure. Keep pretending you're employable, you no-talent leech on society.

>>48
keep pretending you are productive. Use your tunnel vision to prevent yourself from discovering better alternatives. Learn to live with problems, rather than employing known solutions for them.

>>47
D is shit, C++ is worse.  If it ain't Lisp, it's crap.  Lisp is shit.

>>50
whenever people list quotes of famous programmers who hate C++, its always these academics who have never worked in the commercial software industry and only do AI research alone in their office. The two exceptions being Linus Torvalds and Ken Thompson who are both systems programmers, systems programming being the only area C holds an advantage over C++

>>50
Youve won /prog/ after a few weeks of fighting it i give in.  Im going to learn lisp

>>52
I learned Lisp because of /prog/ and I haven't used it for anything but toy programs.

>>51
commercial software industry
stopped reading right there.

>>52
ok, but don't have high expectations.

>>55
I expect it to be shit

Call me a newbie, but what is Lips best used for anyways? AI?

>>57
Lips are good for talking, eating, and kissing. Though kissing is not something a /prog/rider would use them for.

>>45
It all started with a claim that C++ could be made as safe as any other language.

C++ is already too large and complicated for our taste.
- X3J16 (C++ standardization committee)

I really like C++. I was instantly attracted to it back in 1986, and created the first native C++ compiler (Zortech C++).
- Walter Bright

No Unicode.
No networking.
No default GUI toolkit.
Piss poor, incomplete implementations, all of them.

Use only for systems programming and game development. Any other uses are sadomasochism.

C++11 fixes the major issues that C++ had. It doesn't really take longer to write (than C#, Java, etc.) if you know what you're doing, and you get all the efficiency of C++.

All play and no work makes Jack a wise man.

>>61
Please understand that these things are outside the scope of the language (except UNICODE, since they have a string class, and I believe this has been implemented half-assedly in C++11). That said, if C++ just had a nice set of standard namespaced libraries you could statically link to to support these things, like Haskell for example, it would eliminate one of the worst problems with C++. After that of course, there's still the godawful syntax and shit heaps of duplicate functionality.

Rei.

>>64
For me, it's UMENA HASKAL-CHAN!!

Rei.

>>61
it's called third party libraries you dickfuckcuntmong.

C++ a shit

>>68
obvious Java/C# Enterprise Programmer who expects all libraries to be built in to the language implementation

bumpu pantsu

Cons: no cons cell

bumpu pantsu

Rei.

bampu pantsu

bampu pantsu

bampu pantsu

Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy