Writing Classes in AP Computer Science A

Statements

Comments

Annotations

Directives

To provide step-by-step instructions on how to compile and run the program.

To automatically generate standardized API documentation from source code.

To add detailed explanations inside methods for complex algorithms.

To indicate changes and updates made during different versions of the program.

Block comments

Multi-line comments

Single-line comments

Javadoc comments

Recursive solution used for educational purposes though iterative may be more efficient due to stack overflow risk with large inputs.

Recursion chosen as it enables parallel computation of Fibonacci numbers yielding faster runtime on multi-core processors.

Iterative version avoided because recursion offers better space complexity by reducing variable usage within loops.

Recursion provides a clearer and more concise code structure, which outweighs any efficiency gains from iteration.

QuickSort is selected due to its inherent simplicity and ease of implementation in comparison to other sorting algorithms.

We use QuickSort as it guarantees $O(n \log n)$ time complexity in the worst-case scenario, unlike others.

QuickSort's ability to sort without additional memory makes it the preferred choice over MergeSort or HeapSort.

QuickSort is chosen for its $O(n \log n)$ average time complexity, making it efficient for large datasets.

The final classes are immutable, preventing further extension through additional subclassing or modification.

There could be increased complexity due to deep hierarchy trees which can make maintenance difficult.

Objects become less reusable because they are limited to single-inheritance structures in certain languages like Java.

Performance overhead increases dramatically as objects require more memory space due to inherited properties.

Developers choose composition to achieve flexibility by combining object behaviors at runtime.

Using inheritance can lead to tightly coupled code which is harder to maintain than using composition.

Composition reduces the ability for different parts of a program to interact and communicate data.

They prefer composition as it simplifies the creation of subclasses with additional functionality.

The parameters used by a method.

The return value type and its meaning.

A description of what a method does.

The author's personal opinion about unrelated topics.

Customers who purchased software products.

People looking for entertainment while reading source codes.

Computers that compile your source codes.

Other developers who may read or maintain your code.

At the end of each line of code for clarification purposes only.

After main method declaration exclusively.

Typically before a block of code to explain its purpose or logic.

In random locations as long as it's somewhere within your class file.