Documentation required for commissioned software (product) [closed]
Closed 10 years ago.
Specification languages vs automated tests
I recently listened to an episode of Software Engineering Radio in which Leslie Lamport was interviewed. One thing he discussed was his specification language, TLA+.
How big can the binary code be?
Where does binary go in a computer? When you turn the computer on it points to the bios and runs through it. I get that. Then it loads data off something ( disk, flash, etc. ). But where does it go? Does the binary go in ram? Does that mean if my program is 2mb and ram is 32mb I can only address 30mb? I mainly want to know so I can tell how big my bin can be.
Seeking advice writing functional requirements [duplicate]
This question already has answers here: How should I go about learning a very large and complex application? [duplicate] (9 answers) How do you dive into large code bases? (31 answers) Closed 9 years ago. I inherited a project that I’ve been maintaining for approximately a year now. The project primarily revolves around performing various […]
Seeking advice writing functional requirements [duplicate]
This question already has answers here: How should I go about learning a very large and complex application? [duplicate] (9 answers) How do you dive into large code bases? (31 answers) Closed 9 years ago. I inherited a project that I’ve been maintaining for approximately a year now. The project primarily revolves around performing various […]
The source is the documentation – part 1 [closed]
Closed 9 years ago.
Where is it specified that Java is call by value?
I know that Java is by default call-by-value but I am not sure where in the Java Language Specification this is addressed. Google searching only seems to find me unofficial sources but never points to where the actual part of the specification that describes this is.
What is meant by “redundant, but not duplicative” in the Steelman language requirements?
The Steelman language requirements have this:
How to deal with historic exception specifications in maintained C++ code
Today, I discovered a few exception specifications in legacy code I’ve to maintain, when Cppcheck 1.68 ([Inconclusive]
but correctly) pointed out that the specified exceptions are not handled in specific portions of the code.
How to deal with historic exception specifications in maintained C++ code
Today, I discovered a few exception specifications in legacy code I’ve to maintain, when Cppcheck 1.68 ([Inconclusive]
but correctly) pointed out that the specified exceptions are not handled in specific portions of the code.