Comment Re:Hyperbole Sunday (Score 1) 227
The classic joke was:
I went to the fights and a hockey game broke out
The classic joke was:
I went to the fights and a hockey game broke out
> Inline specifically means "export this as a weak symbol".
Oh gee, and here I thought it meant merge basic blocks. Do you know _anything_ how C++ compilers even work??
>> I can chose between Microsoft's __inline or GCC god-awful __attribute__((always_inline)) syntax.
> Yes, but why are you trying to do that? You're fighting the optimizer and you're almost certain to lose.
You love to constantly make incorrect and incomplete assumptions.
1. I want to write ONE directive not clutter my code up with hacks PER compiler. _Why_ do standards exist ? To make everyone's live _easier_.
2. Gee, why do things like _Profiling_ exist. The *compiler* doesn't have access to *run-time* performance. The optimizer is dealing with a _subset_ of data. It doesn't know the "function temperature".
But go on keeping making excuses. You really don't have a clue.
Sadly that's an accurate summary of the problem caused by First-Past-the-Post voting.
One solution is run-off voting or the Alternative vote.
> they lose their IP to someone, and the name Ubisoft becomes a curseword...
You mean Ubisucks already isn't?
When companies can "effectively" just "buy laws" (and/or Politicians) corruption knows no bounds for price gouging.
Great PS4 Link !
I shipped a few games on Wii; wrote an OpenGL implementation for it layering it on top of GX. Interesting that Wii U still uses GX !
> How many usable DirectX bindings do you know for Java?
1. And who's job is that to support DirectX?
2. If Microsoft was _serious_ about DirectX they would add D3D bindings to Java.
> they can as well rewrite Minecraft from the scratch in C++
That was _already_ done for the PS3 and XBox360 versions.
Do you _actually_ use different compiles on different platforms at all ????
'inline' is only a hint
I can chose between Microsoft's __inline or GCC god-awful __attribute__((always_inline)) syntax.
This the reason #define macro's haven't died. 100% guarantee inlining.
Do you even understand the point of having "standards" ??
You're constantly complaining about "breaking things." Gee, if only there was a way to migrate, mitigate, and deploy change
* http://www.volvoclub.org.uk/hi...
This isn't rocket science -- let alone basic computer science. A dead-line is set, we inform people, and we make the switch. It's not fucking hard.
>> Standardized error messages
> doing something that no one else has ever done.
Gee, why does Microsoft provide a _specific_ number for _each_ warning ???
* https://msdn.microsoft.com/en-...
Do you even code in C++??
>> *"A Proposal to Add 2D Graphics Rendering and Display to C++"
> The C++ committee have their heads up their asses because they discuss a proposal submitted according to the correct procedure??
This is a solution in search of a problem.
Do you even _understand_ the term: Kitchen Sink or Over-engineering??
We already have graphics libraries, OpenGL / OpenGL ES, DirectX, etc. We don't need more shit in an already bloated language.
People like you are precisely part of the problem with C++.
1. Completely failing to understand _practical_ matters.
2. Continue to make excuses for why their tools are crap.
3. And then post blatantly false information that gets modded up to Insightful without a clue.
/Oblg.
Rocks "Das Rad" -- "Human civilization from the rocks perspective"
https://www.youtube.com/watch?...
> I can't think of a single game today that uses OpenGL.
Uh, HELLO McFly; Minecraft. That "insignificant" game that "only" sold 54+ million copies. ~18 MILLION on PC.
> Why is that?
Because you didn't even be bothered to spend 2 seconds to look
Gee, what is Valve using on OSX, and Linux !?!?
For God's sake, stop researching for a while and begin to think!