False,
" I am talking about 20-30+ millions lines of code, software at the scale and complexity of Autodesk Maya for example.
If you freeze the development as long as it needs to be, can you actually fix all the bugs until there is simply not a single bug, if such a thing could be verified by computers? What are the arguments for and against the existence of a bug-free system?
Because there is some notion that every fix you make creates more bugs, but I don't think that's true.
By bugs I meant from the simplest typos in the UI, to more serious preventative bugs that has no workaround. For example a particular scripting function calculates normal incorrectly. Also even when there are workarounds, the problem still has to be fixed. So you could say you can do this particular thing manually instead of using the provided function but that function still has to be fixed."
work cited:
https://softwareengineering.stackexchange.com/questions/195571/is-it-possible-to-reach-absolute-zero-bug-state-for-large-scale-software
Answer:
closed sounds right, dobt take my word for it doe
Answer:
src attribute of image tag specifies the url of an image.
Some computer engineering students decided to revise the LC-3 for their senior project. KBSR and the DSR into one status register: the IOSR (the input/output status register). IOSR[15] is the keyboard device Ready bit and IOSR[14] is the display device Ready bit can be done in LC-3.
LC-4 is a poor design.
Explanation:
LC-3, is a type of computer educational programming language, an assembly language, which is a type of low-level programming language.
It features a relatively simple instruction set, but can be used to write moderately complex assembly programs, and is a theoretically viable target for a C compiler. The language is less complex than x86 assembly but has many features similar to those in more complex languages. These features make it useful for beginning instruction, so it is most often used to teach fundamentals of programming and computer architecture to computer science and computer engineering students.
The LC-3 specifies a word size of 16 bits for its registers and uses a 16-bit addressable memory with a 216-location address space. The register file contains eight registers, referred to by number as R0 through R7. All of the registers are general-purpose in that they may be freely used by any of the instructions that can write to the register file, but in some contexts (such as translating from C code to LC-3 assembly) some of the registers are used for special purposes.
When a character is typed:
- Its ASCII code is placed in bits [7:0] of KBDR (bits [15:8] are always zero)
- The “ready bit” (KBSR[15]) is set to one
- Keyboard is disabled -- any typed characters will be ignored
When KBDR is read:
- KBSR[15] is set to zero
- Keyboard is enabled
- Alternative implementation: buffering keyboard input
Answer:
You can answer this very easily by considering which of the circumstances affect the end user and which affect the developer:
1) Didn't use comments in the code
- affects developers
2) User complaints about language used in the program
- affects users
3) The variables have meaningless names
- affects developers
4) The program should have used a loop
- affects developers
5) The numeric results are incorrect
- affects users
Your answers then are 2 and 5, spoken languages and incorrect output will very much affect the user experience.
