4 ms·
There is a difference between a program with a specification/documentation outlining what it should do, and one that doesn't have a spec. AFAIK, hello.c doesn'
by usrbinbash 5y ago
There is a difference between a program with a specification/documentation outlining what it should do, and one that doesn't have a spec.
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.
- admax88qqq 5y agoSo if I don't write a spec, I have no bugs. Got it.
- ericHosick 5y agoThis Porsche has a design flaw: I can only go 22,500 kilometers before I have to replace the tires. This VW bus has a design flaw: I can't pull more than 1G on the race track.
- dancemethis 5y agoSpeak for yourself on the bus...
- usrbinbash 5y agoWhere did I say that? 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.