Introducing Vulkan-Hpp – Open-Source Vulkan C++ API

Post by pjmlp » Sun, Jul 24, 2016, 7:07 AM UTC

shmerl wrote: post #59

pjmlp wrote: post #58

Earlier quoted context omitted.

What people? Indies and FOSS activists that probably still write M$ to this day and believe that Sony and Nintendo or even Sega in its former days are any different. I really bet none of those ever walked the floors of GDC.

> What people? Anyone who thinks and cares about progress and doesn't drink Koolaid served by MS and Co. Surely not lock-in freaks, who frame their tax on the industry as something positive. > I really bet none of those ever walked the floors of GDC. You sound like GDC is owned by MS, or it's ought to be. Are you paid by them? Either way, it's a very poor way to measure opinions or their value. Find something better.

Post by pjmlp » Sun, Jul 24, 2016, 7:58 AM UTC

shmerl wrote: post #62

pjmlp wrote: post #61

Earlier quoted context omitted.

No, I am someone that in a past life was allowed to spend some time in the backstage how big boys do games and still keep some of those ties, even though I just do IT enterprise consulting nowadays. No one in GDC hallways speak of lock-in as activists believe they do.

> No one in GDC hallways speak of lock-in as activists believe they do. There were many talks on GDC about Vulkan which discussed lock-in issues that it can solve.

Post by skocznymroczny » Sun, Jul 24, 2016, 9:43 AM UTC

lubesGordi wrote: post #21

lubesGordi wrote: post #7

Vulkan is an NVIDIA gpu api. https://www.khronos.org/vulkan/

Whoa holy smokes yeah I missed the mark on that one. So Vulkan is a replacement for openGL, essentially a new api to gpu's in general? Is that closer to it? In the future I'll phrase the statement as a question if I'm not 100% clear on it. Sorry for the noise.

Post by IshKebab » Sun, Jul 24, 2016, 10:55 AM UTC

sjolsen wrote: post #64

Hello71 wrote: post #31

So hold on. Assuming that I understand C++ linking right, you're saying that I should include this 17000-line file in every single cpp unit in my application that uses Vulkan APIs? And people wonder why C++ programs compile so slowly.

>And people wonder why C++ programs compile so slowly. People have been aware of this problem for some time. It's one of the reasons the C++ community is trying to develop a proper module system (or was the last time I checked, which was a while back).

Post by loeg » Sun, Jul 24, 2016, 1:19 PM UTC

banachtarski wrote: post #42

loeg wrote: post #39

Earlier quoted context omitted.

It isn't type-safe in the sense you're used to in C++. But common pitfalls can be avoided if you don't destroy the type information by assigning through a vanilla integer. enum a { A }; enum b { B }; static enum a a = B; $ clang -Wenum-conversion -Werror a.c b.c:4:19: error: implicit conversion from enumeration type 'enum b' to different enumeration type 'enum a' [-Werror,-Wenum-conversion] static enum a a = B; ~ ^ 1…

The easy ability to assign it to a vanilla integer or cast it implicitly (through an arithmetic operator or comparison for example) is what I mean when I say they aren't typesafe. A warning is also a fair bit weaker than a flat out compile error, although I'll grant that compiling with -Werror (a really challenging thing for most companies) alleviates that.