That makes sense, I never used gcc without -Wall and -pedantic and so on, so I just take a lot of warnings for granted, including discarded return values. Still, I'm not totally sure I understand the need for this [[nodiscard]] pragma, seems pretty verbose for not much practical benefit.
documentation purposes mostly, for example to show that a function call is useless if you dont use the return value (theres no way to declare a function pure without using compiler extensions)
My most common pattern for using nodiscard is when I have an outparam being written to, and the actual return value represents the success or failure of the operation.
Do those exist still?
yeah theres like unix service system or unix system services or whatever
humble me when i was bored that one time and wanted to try cobol for shits and giggles
Eh, I betcha the odd autist that has the manual memorized and knows all the specific hardware bugs and whatnot still exists, not sure if you'll lure him out of the basement though. I was doubtful that it is even feasible to learn cobol nowadays, because I thought it would have to be incredibly hard to even run. But apparently you can just download GnuCOBOL and go ham, impressive.
GCC 15 has introduced gcobol, which compiles COBOL directly to a native executable instead of first transpiling it to C
In my experience, that is what shops with weirdo languages actually do in practice, even if the job ad says otherwise. In big shops like banks (or in this case a consultancy), the job ad is written by someone who doesn't know anything about the topic and just goes off a bunch of given keywords, which is how you get asked for N+2 years of experience in a technology that was invented N years ago or "JSON programming experience".
*stretches*
so hes still writing it
#include "stdafx.h"
#include "com.mojang.nbt.h"
#include "Abilities.h"
Abilities::Abilities()
{
invulnerable = false;
flying = false;
mayfly = false;
instabuild = false;
mayBuild = true;
flyingSpeed = 0.05f;
walkingSpeed = 0.1f;
#ifdef _DEBUG_MENUS_ENABLED
debugflying = false;
#endif
}
void Abilities::addSaveData(CompoundTag *parentTag)
{
CompoundTag *tag = new CompoundTag();
tag->putBoolean(L"invulnerable", invulnerable);
tag->putBoolean(L"flying", flying);
tag->putBoolean(L"mayfly", mayfly);
tag->putBoolean(L"instabuild", instabuild);
tag->putBoolean(L"mayBuild", mayBuild);
tag->putFloat(L"flySpeed", flyingSpeed);
tag->putFloat(L"walkSpeed", walkingSpeed);
parentTag->put(L"abilities", tag);
}
void Abilities::loadSaveData(CompoundTag *parentTag)
{
if (parentTag->contains(L"abilities"))
{
CompoundTag *tag = parentTag->getCompound(L"abilities");
invulnerable = tag->getBoolean(L"invulnerable");
flying = tag->getBoolean(L"flying");
mayfly = tag->getBoolean(L"mayfly");
instabuild = tag->getBoolean(L"instabuild");
if (tag->contains(L"flySpeed"))
{
flyingSpeed = tag->getFloat(L"flySpeed");
walkingSpeed = tag->getFloat(L"walkSpeed");
}
if (tag->contains(L"mayBuild"))
{
mayBuild = tag->getBoolean(L"mayBuild");
}
}
}
float Abilities::getFlyingSpeed()
{
return flyingSpeed;
}
void Abilities::setFlyingSpeed(float value)
{
this->flyingSpeed = value;
}
float Abilities::getWalkingSpeed()
{
return walkingSpeed;
}
void Abilities::setWalkingSpeed(float value)
{
this->walkingSpeed = value;
}
return flyingSpeed;
}
void Abilities::setFlyingSpeed(float value)
{
this->flyingSpeed = value;
}
float Abilities::getWalkingSpeed()
{
return walkingSpeed;
}
void Abilities::setWalkingSpeed(float value)
{
this->walkingSpeed = value;btw the PS3 edition leak is a neutered version of the legacy console version