Is there no such thing as a bug then? The program does what the code says so every "misbehavior" and crash is expected behavior.
AFAIK, hello.c doesn't have a spec, so the code is the spec. If I am using it, I have to read the code to know what it does.
This VW bus has a design flaw: I can't pull more than 1G on the race track.
I said if a software doesn't have a spec, the code IS the spec.
If I hand out a sheet of paper saying "the program returns X", but running it returns Y instead, the program is buggy.
If I hand out a piece of code which says "return X", and someone runs it expecting it to return Y, thats not the codes problem.