Sup Forums the programmer

>VK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_STATE_CREATE_INFO

If you were to design a C API, could you come up with a better name for that constant?

vk_stpvisci

Nope. It describes, in excruciating detail, exactly what it is and what it's for. You couldn't give it a better name.

vk_vistate

You do realize long names, besides looking retarded, are difficult to memorize and type out? Of course a CS graduate has no idea

beautiful

>memorize and type out
IDEs have progressed past Notepad.exe, user.

VK_STRUCT_TYPE_PIPELINE_VERTEX_INPUT_STATE_CREATE_INFO

There is no such thing as a structure in C.

>I can't code without autocomplete

You can't program period.

If you knew what you were doing you would automatically know how to type something like that.

>i'm stuck in the last generation

did you know threre's a 2nd edition of k&r? check it out.

>what is a struct
>are you a dumb nigger

You're one of those programmers that type one or two letters and begin scrolling through the autocomplete window over 100s of macros with similarly looking names (as is the case with the Vulkan API) and finding what you're looking for eons later and repeating the process next time you need it again?

Who's saying anything about having to memorize this shit? It's boilerplate stuff that you only have to deal with within the contexts where they appear, i.e. in the boilerplate code.

Also, if you haven't noticed, VK struct names follow a logical pattern that makes them easy to remember: The prefix describes type (VK_STRUCTURE_TYPE), the suffix (CREATE_INFO) describes what it's for, and the stuff in the middle describes which part of the API this one belongs to.

3rd, and while it's already been mentioned that IDE's can catch typos like this, modern compilers like clang and later versions of GCC can in many cases also catch them and offer the correct spelling as a suggestion.

structs aren't real, they're just a compiler abstraction for byte offsets in a single monolithic block of bytes

i'm one of those programmers that uses the best tools i can find to help me get my job done

OP (who is a faggot) already tried this shitty thread yesterday.

Pretty obvious it's just another Novidya shill trying to push anti-Vulkan agenda because their hardware flat out runs worse on DX12/Vulkan games.

Their argument is fucking retarded and would only convince a complete drooler that Vulkan is "bad" because it has descriptive API function names.

>memorize and type out
>implying that you're not the CS graduate
Don't they teach you about Vim/Emacs/FuckingEverything auto-complete.

they're a bisonshit

Sounds like you're using a shitty editor.

Is it any worse than OpenGL?
You have to write at least 300 lines of boilerplate in gl before you can even open a gl context with a triangle in it.

uh

if you have to ask, you're better off not knowing

... lern2struct user

>They don't see that STRUCTURE was replaced with STRUCT

Not even those nice dubs can save you from the embarrassment.

the dubs got the right answer

>type out
Just use ur ide lol

You sound like a retard that's probably not actually hireable anywhere

> name > 31 characters
That's actually forbidden by some rules, and is non-portable.

symbol names longer than 8 characters are non-portable

>not using the official Vulkan.hpp which makes code a lot more cleaner
Bitch

A vulkan triangle is like 1k lines of boilerplate.

>COMPUTER_THINGY_1
We make however many "COMPUTER THINGIES" for each method, function, object, etc. in the default library. We don't tell anyone what they do, we simply let them find out on their own. Eventually we will have entire books published about the "COMPUTER_THINGY" format for C, and people will be arguing about the meaning of each one. Then we sell our compiler/IDE for profit to all the normies who want to jump on the Sup Forums train because they saw a news title "COMPLEX AND MYSTICAL COMPUTER LANGUAGE, WHO CAN FIGURE IT OUT? INTERNET IN FLAMES"

Every low level 3d rendering api in a nutshell

This. It even sets the shitty create info automatically with some completime magic.

>completime

I declare you retarded.

Internal identifiers and macro names are allowed to be a maximum of 63 characters.

The ISO C11 standard, which has all mandatory features supported in full by GCC, Clang, and the Small Device C Compiler (SDCC), allows internal identifiers to be a maximum of 63 characters, and external identifiers to be a maximum of 31 characters. Considering that most platforms, including both obscure embedded platforms and mainstream platforms are supported by at least one of these three free-as-in-freedom compilers, there is no legitimate reason to restrict one's self to older standards of C for "portability".

>got my head-less vulkan boiler plate setup in C++ using vulkan.hpp
>gotta implement a "screenshot" feature just to see if it actually rendered before I dig in and give it a little personal API
>all this shit involving memory locations and transfering between optimal to linear textures and shit

it's verbose as hell but in a way it's fun. "It's an API with no secrets" as Intel put it.

DirectX and OpenGL are made with such a software and games bias for their abstractions that having vulkan which is "to the metal" of the GPU just feels nicer knowing the only bias the API has is "do you want COMPUTE or GRAPHICS".

It's not for kids making engines. If anything it's the last API you would implement in your game engine or software's graphical layer but at least I can get the GPU to do "exactly what I want" rather than "how opengl does it" and "how directx does it". Hell you can implement opengl and directx in vulkan.

why does it matter? i for one like pretty descriptive constant naming, its not like you have to know its name (any decent editor will have auto-complete) or care about its compilation (its a constant, its name wont matter for the release build)