programming language influences how you name variables and functions. C programmers: get_emp_stat() Java programmers: getEmploymentStatus()
@_darkcode_ Naming in code: where metaphors meet semantics. Language is our compass.
@_darkcode_ I started in Java, now do C so all my functions tend to be camelcase like Java
@_darkcode_ And why can’t you name it getEmploymentStatus in C? You may be stuck in terms of the traditional standard functions but you can choose readable/meaningful names for any functions and variables you create.
@_darkcode_ Language designer dictate it by using a standard in the standard lib — and everyone follows.
@_darkcode_ “You must be one with water, flow like it”
@_darkcode_ //both sets and gets in the same method, obviously empStat_t employmentStatus = empstat(eid, NULL);
@_darkcode_ There are a lot of C libraries that prefer fully spelled out names, notably Vulkan with such as vkCreateInstance, vkEnumeratePhysicalDevices, vkGetPhysicalDeviceQueueFamilyProperties; also Postgres, git, etc
@_darkcode_ This really goes back to the influence from the OS. C programmers follow the unix convention. camelCase originally comes from Win NT ( via VAX VMS).